Methods and systems for mapping data items to sparse distributed representations

ABSTRACT

A method of mapping data items to sparse distributed representations (SDRs) includes clustering in a two-dimensional metric space, by a reference map generator, a set of data documents selected according to at least one criterion, generating a semantic map. The semantic map associates a coordinate pair with each of the set of data documents. A parser generates an enumeration of data items occurring in the set of data documents. A representation generator determines, for each data item in the enumeration, occurrence information. The representation generator generates a distributed representation using the occurrence information. A sparsifying module receives an identification of a maximum level of sparsity. The sparsifying module reduces a total number of set bits within the distributed representation based on the maximum level of sparsity to generate an SDR having a normative fillgrade.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. patent application Ser. No.62/034,269, filed on Aug. 7, 2014, entitled “Methods and Systems forMapping Data Items to Sparse Distributed Representations,” and to U.S.Provisional Patent Application Ser. No. 62/134,202, filed on Mar. 17,2015, entitled “Methods and Systems for Enhancing Search Systems,” eachof which is hereby incorporated by reference.

BACKGROUND

The disclosure relates to generating cross-lingual sparse distributedrepresentations. More particularly, the methods and systems describedherein relate to functionality for generating mappings of terms tosparse distributed representations (SDRs) and associating translationsof the terms with the generated mappings.

In conventional systems, the use of self-organizing maps is typicallylimited to clustering data documents by type and to either predictingwhere an unseen data document would be clustered to, or analyzing thecluster structure of the used data document collection. Suchconventional systems do not typically provide functionality for usingthe resulting “clustering map” as a “distributed semantic projectionmap” for the explicit semantic definition of the data document'sconstituent data items.

BRIEF SUMMARY

In one aspect, a computer-implemented method of mapping data items tosparse distributed representations includes clustering in atwo-dimensional metric space, by a reference map generator, executing ona computing device, a set of data documents selected according to atleast one criterion. The method includes associating, by the referencemap generator, a coordinate pair with each of the set of data documents.The method includes generating, by a parser executing on the computingdevice, an enumeration of data items occurring in the set of datadocuments. The method includes determining, by a representationgenerator executing on the computing device, for each data item in theenumeration, occurrence information including: (i) a number of datadocuments in which the data item occurs, (ii) a number of occurrences ofthe data item in each data document, and (iii) the coordinate pairassociated with each data document in which the data item occurs. Themethod includes generating, by the representation generator, adistributed representation using the occurrence information. The methodincludes receiving, by a sparsifying module executing on the computingdevice, an identification of a maximum level of sparsity. The methodincludes reducing, by the sparsifying module, a total number of set bitswithin the distributed representation based on the maximum level ofsparsity to generate a sparse distributed representation having anormative fillgrade.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, aspects, features, and advantages ofthe disclosure will become more apparent and better understood byreferring to the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1A is a block diagram depicting an embodiment of a system formapping data items to sparse distributed representations;

FIG. 1B is a block diagram depicting one embodiment of a system forgenerating a semantic map for use in mapping data items to sparsedistributed representations;

FIG. 1C is a block diagram depicting one embodiment of a system forgenerating a sparse distributed representation for a data item in a setof data documents;

FIG. 2 is a flow diagram depicting an embodiment of a method for mappingdata items to sparse distributed representations;

FIG. 3 is a block diagram depicting one embodiment of a system forperforming arithmetic operations on sparse distributed representationsof data items generated using data documents clustered on semantic maps;

FIG. 4 is a flow diagram depicting one embodiment of a method foridentifying a level of semantic similarity between data items;

FIG. 5 is a flow diagram depicting one embodiment of a method foridentifying a level of semantic similarity between a user-provided dataitem and a data item within a set of data documents;

FIG. 6A is a block diagram depicting one embodiment of a system forexpanding a query provided for use with a full-text search system;

FIG. 6B is a flow diagram depicting one embodiment of a method forexpanding a query provided for use with a full-text search system;

FIG. 6C is a flow diagram depicting one embodiment of a method forexpanding a query provided for use with a full-text search system;

FIG. 7A is a block diagram depicting one embodiment of a system forproviding topic-based documents to a full-text search system;

FIG. 7B is a flow diagram depicting one embodiment of a method forproviding topic-based documents to a full-text search system;

FIG. 8A is a block diagram depicting one embodiment of a system forproviding keywords associated with documents to a full-text searchsystem for improved indexing;

FIG. 8B is a flow diagram depicting one embodiment of a method forproviding keywords associated with documents to a full-text searchsystem for improved indexing;

FIG. 9A is a block diagram depicting one embodiment of a system forproviding search functionality for text documents;

FIG. 9B is a flow diagram depicting one embodiment of a method forproviding search functionality for text documents;

FIG. 10A is a block diagram depicting one embodiment of a systemproviding user expertise matching within a full-text search system;

FIG. 10B is a block diagram depicting one embodiment of a systemproviding user expertise matching within a full-text search system;

FIG. 10C is a flow diagram depicting one embodiment of a method formatching user expertise with requests for user expertise;

FIG. 10D is a flow diagram depicting one embodiment of a method for userprofile-based semantic ranking of query results received from afull-text search system;

FIG. 11A is a block diagram depicting one embodiment of a system forproviding medical diagnosis support;

FIG. 11B is a flow diagram depicting one embodiment of a method forproviding medical diagnosis support;

FIGS. 12A-12C are block diagrams depicting embodiments of computersuseful in connection with the methods and systems described herein;

FIG. 12D is a block diagram depicting one embodiment of a system inwhich a plurality of networks provide data hosting and deliveryservices;

FIG. 13 is a block diagram depicting one embodiment of a system forgenerating cross-lingual sparse distributed representations;

FIG. 14A is a flow diagram depicting an embodiment of a method fordetermining similarities between cross-lingual sparse distributedrepresentations; and

FIG. 14B is a flow diagram depicting an embodiment of a method fordetermining similarities between cross-lingual sparse distributedrepresentations.

DETAILED DESCRIPTION

In some embodiments, the methods and systems described herein providefunctionality for generating mappings of terms to sparse distributedrepresentations (SDRs) and associating translations of the terms withthe generated mappings.

Referring now to FIG. 1A, a block diagram depicts one embodiment of asystem for mapping data items to sparse distributed representation. Inbrief overview, the system 100 includes an engine 101, a machine 102 a,a set of data documents 104, a reference map generator 106, a semanticmap 108, a parser and preprocessing module 110, an enumeration of dataitems 112, a representation generator 114, a sparsifying module 116, oneor more sparse distributed representations (SDRs) 118, a sparsedistributed representation (SDR) database 120, and a full-text searchsystem 122. In some embodiments, the engine 101 refers to all of thecomponents and functionality described in connection with FIGS. 1A-1Cand 2.

Referring now to FIG. 1A, and in greater detail, the system includes aset of data documents 104. In one embodiment, the documents in the setof data documents 104 include text data. In another embodiment, thedocuments in the set of data documents 104 include variable values of aphysical system. In still another embodiment, the documents in the setof data documents 104 include medical records of patients. In anotherembodiment, the documents in the set of data documents 104 includechemistry-based information (e.g., DNA sequences, protein sequences, andchemical formulas). In yet another embodiment, each document in the setof data documents 104 includes musical scores. The data items withindata documents 104 may be words, numeric values, medical analyses,medical measurements, and musical notes. The data items may be stringsof any type (e.g., a string including one or more numbers). The dataitems in a first set of data documents 104 may be different languagethan the data items in a second set of data documents 104. In someembodiments, the set of data documents 104 includes historic log data. A“document” as used herein may refer to a collection of data items eachof which corresponds to a system variable originating from the samesystem. In some embodiments, system variables in such a document aresampled concurrently.

As indicated above the use of “data item” herein encompasses words asstring data, scalar values as numerical data, medical diagnoses andanalyses as numeric data or class-data, musical notes and variables ofany type all coming from a same “system.” The “system” may be anyphysical system, natural or artificial, such as a river, a technicaldevice, or a biological entity such as a living cell or a humanorganism. The system may also be a “conceptual system” such as alanguage or web server log-data. The language can be a natural languagesuch as English or Chinese, or an artificial language such as JAVA orC++ program code. As indicated above, the use of “data document”encompasses a set of “data items.” These data items may beinterdependent by the semantics of the underlying “system.” Thisgrouping can be a time based group, if all data item values are sampledat the same moment; for example, measurement data items coming from theengine of a car can be sampled every second and grouped into a singledata document. This grouping can also be done along a logical structurecharacterized by the “system” itself, for example in natural language,word data items can be grouped as sentences, while in music, data itemscorresponding to notes can be grouped by measures. Based on these datadocuments, document vectors can be generated by the above methods (oraccording to other methods as understood by those of ordinary skill inthe art) in order to generate a semantic map of the “system,” as will bedescribed in greater detail below. Using this “system,” semantic mapdata item SDRs can be generated, as will be described in greater detailbelow. All of the methods and systems described below may be applied toall types of data item SDRs.

In one embodiment, a user selects the set of data documents 104according to at least one criterion. For example, the user may selectdata documents for inclusion in the set of data documents 104 based uponwhether the data documents relate to a particular subject matter. Asanother example, the set of data documents 104 represents a semanticuniverse in which the system 100 will be used. In one embodiment, theuser is a human user of the system 100. In another embodiment, themachine 100 executes functionality for selecting data documents in theset of data documents 104.

The system 100 includes a reference map generator 106. In oneembodiment, the reference map generator 106 is a self-organizing map. Inanother embodiment, the reference map generator 106 is a generativetopographic map. In still another embodiment, the reference mapgenerator 106 is an elastic map. In another embodiment, the referencemap generator 106 is a neural gas type map. In still another embodiment,the reference map generator 106 is any type of competitive,learning-based, unsupervised, dimensionality-reducing, machine-learningmethod. In another embodiment, the reference map generator 106 is anycomputational method that can receive the set of data documents 104 andgenerate a two-dimensional metric space on which are clustered pointsrepresenting the documents from the set of data documents 104. In stillanother embodiment, the reference map generator 106 is any computerprogram that accesses the set of data documents 104 to generate atwo-dimensional metric space on which every clustered point represents adata document from the set of data documents 104. Although typicallydescribed herein as populating a two-dimensional metric space, in someembodiments, the reference map generator 106 populates an n-dimensionalmetric space. In some embodiments, the reference map generator 106 isimplemented in software. In other embodiments, the reference mapgenerator 106 is implemented in hardware.

The two-dimensional metric space may be referred to as a semantic map108. The semantic map 108 may be any vector space with an associateddistance measure.

In one embodiment, the parser and preprocessing module 110 generates theenumeration of data items 112. In another embodiment, the parser andpreprocessing module 110 forms part of the representation generator 114.In some embodiments, the parser and preprocessing module 110 isimplemented at least in part as a software program. In otherembodiments, the parser and preprocessing module 110 is implemented atleast in part as a hardware module. In still other embodiments, theparser and preprocessing module 110 executes on the machine 102. In someembodiments, a parser and preprocessing module 110 may be specializedfor a type of data. In other embodiments, a plurality of parser andpreprocessing modules 110 may be provided for a type of data.

In one embodiment, the representation generator 114 generatesdistributed representations of data items. In some embodiments, therepresentation generator 114 is implemented at least in part as asoftware program. In other embodiments, the representation generator 114is implemented at least in part as a hardware module. In still otherembodiments, the representation generator 114 executes on the machine102.

In one embodiment, the sparsifying module 116 generates a sparsedistributed representation (SDR) of a data item. As will be understoodby one of ordinary skill in the art, an SDR may be a large numeric(binary) vector. For example, an SDR may have several thousand elements.In some embodiments, each element in an SDR generated by the sparsifyingmodule 116 has a specific semantic meaning. In one of these embodiments,vector elements with similar semantic meaning are closer to each otherthan semantically dissimilar vector elements, measured by the associateddistance metric.

In one embodiment, the representation generator 114 provides thefunctionality of the sparsifying module 116. In another embodiment, therepresentation generator 114 is in communication with a separatesparsifying module 116. In some embodiments, the sparsifying module 116is implemented at least in part as a software program. In otherembodiments, the sparsifying module 116 is implemented at least in partas a hardware module. In still other embodiments, the sparsifying module116 executes on the machine 102.

In one embodiment, the sparse distributed representation (SDR) database120 stores sparse distributed representations 118 generated by therepresentation generator 114. In another embodiment, the sparsedistributed representation database 120 stores SDRs and the data itemthe SDRs represent. In still another embodiment, the SDR database 120stores metadata associated with the SDRs. In another embodiment, the SDRdatabase 120 includes an index for identifying an SDR 118. In yetanother embodiment, the SDR database 120 has an index for identifyingdata items semantically close to a particular SDR 118. In oneembodiment, the SDR database 120 may store, by way of example andwithout limitation, any one or more of the following: a reference numberfor a data item, the data item itself, an identification of a data itemfrequency for the data item in the set of data documents 104, asimplified version of the data item, a compressed binary representationof an SDR 118 for the data item, one or several tags for the data item,an indication of whether the data item identifies a location (e.g.,“Vienna”), and an indication of whether the data item identifies aperson (e.g., “Einstein”). In another embodiment, the sparse distributedrepresentation database 120 may be any type or form of database.

Examples of an SDR database 120 include, without limitation, structuredstorage (e.g., NoSQL-type databases and BigTable databases), HBasedatabases distributed by The Apache Software Foundation of Forest Hill,Md., MongoDB databases distributed by 10 Gen, Inc. of New York, N.Y.,Cassandra databases distributed by The Apache Software Foundation, anddocument-based databases. In other embodiments, the SDR database 120 isan ODBC-compliant database. For example, the SDR database 120 may beprovided as an ORACLE database manufactured by Oracle Corporation ofRedwood City, Calif. In other embodiments, the SDR database 120 can be aMicrosoft ACCESS database or a Microsoft SQL server databasemanufactured by Microsoft Corporation of Redmond, Wash. In still otherembodiments, the SDR database 120 may be a custom-designed databasebased on an open source database, such as the MYSQL family of freelyavailable database products distributed by Oracle Corporation.

Referring now to FIG. 2, a flow diagram depicts one embodiment of amethod 200 for mapping data items to sparse distributed representations.In brief overview, the method 200 includes clustering, by a referencemap generator executing on a computing device, in a two-dimensionalmetric space, a set of data documents selected according to at least onecriterion, generating a semantic map (202). The method 200 includesassociating, by the semantic map, a coordinate pair with each of the setof data documents (204). The method 200 includes generating, by a parserexecuting on the computing device, an enumeration of data itemsoccurring in the set of data documents (206). The method 200 includesdetermining, by a representation generator executing on the computingdevice, for each data item in the enumeration, occurrence informationincluding: (i) a number of data documents in which the data item occurs,(ii) a number of occurrences of the data item in each data document, and(iii) the coordinate pair associated with each data document in whichthe data item occurs (208). The method 200 includes generating, by therepresentation generator, a distributed representation using theoccurrence information (210). The method 200 includes receiving, by asparsifying module executing on the computing device, an identificationof a maximum level of sparsity (212). The method 200 includes reducing,by the sparsifying module, a total number of set bits within thedistributed representation based on the maximum level of sparsity togenerate a sparse distributed representation having a normativefillgrade (214).

Referring now to FIG. 2 in greater detail, and in connection with FIG.1A-1B, the method 200 includes clustering, by a reference map generatorexecuting on a computing device, in a two-dimensional metric space, aset of data documents selected according to at least one criterion,generating a semantic map (202). In one embodiment, the at least onecriterion indicates that data items in the set of data documents 104appear a threshold number of times. In another embodiment, the at leastone criterion indicates that each data document in the set of datadocuments 104 should include descriptive information about the state ofthe system it was derived from. In the case of data documents, the atleast one criterion indicates that each data document should express aconceptual topic (e.g., an encyclopedic description). In anotherembodiment, the at least one criterion indicates that a list ofcharacteristics of the set of data documents 104 should evenly fill outa desired information space. In another embodiment, the at least onecriterion indicates that the set of data documents 104 is originatingfrom the same system. In the case of data documents, the at least onecriterion indicates that the data documents are all in the samelanguage. In still another embodiment, the at least one criterionindicates that the set of data documents 104 be in a natural (e.g.,human) language. In still another embodiment, the at least one criterionindicates that the set of data documents 104 be in a computer language(e.g., computer code of any type). In another embodiment, the at leastone criterion indicates that the set of data documents 104 may includeany type or form of jargon or other institutional rhetoric (e.g.,medicine, law, science, automotive, military, etc.). In anotherembodiment, the at least one criterion indicates that the set of datadocuments 104 should have a threshold number of documents in the set. Insome embodiments, a human user selects the set of data documents 104 andthe machine 102 receives the selected set of data documents 104 from thehuman user (e.g., via a user interface to a repository, directory,document database, or other data structure storing one or more datadocuments, not shown).

In one embodiment, the machine 102 preprocesses the set of datadocuments 104. In some embodiments, the parser and preprocessing module110 provides the preprocessing functionality for the machine 102. Inanother embodiment, the machine 102 segments each of the set of datadocuments 104 into terms and sentences, standardizes punctuation, andeliminates or converts undesired characters. In still anotherembodiment, the machine 102 executes a tagging module (not shown) toassociate one or more meta-information tags to any data item or portionof a data item in the set of data documents 104. In another embodiment,the machine 102 normalizes the text size of a basic conceptual unit,slicing each of the set of data documents 104 into equally sized textsnippets. In this embodiment, the machine 102 may apply one or moreconstraints when slicing the set of data documents 104 into thesnippets. For example, and without limitation, the constraints mayindicate that documents in the set of data documents 104 should onlycontain complete sentences, should contain a fixed number of sentences,should have a limited data item count, should have a minimum number ofdistinct nouns per documents, and that the slicing process shouldrespect the natural paragraphs originating from a document author. Inone embodiment, the application of constraints is optional.

In some embodiments, to create more useful document vectors, the system100 provides functionality for identifying the most relevant data items,from a semantic perspective, of each document in a set of data documents104. In one of these embodiments, the parser and preprocessing module110 provides this functionality. In another embodiment, the referencemap generator 106 receives one or more document vectors and generatesthe semantic map 108 using the received one or more document vectors.For example, the system 100 may be configured to identify and selectnouns (e.g., identifying based on a part-of-speech tag assigned to eachdata item in a document during preprocessing). As another example,selected nouns may be stemmed to aggregate all morphologic variantsbehind one main data item instance (e.g., plurals and case variations).As a further example, a term-frequency-inverse document frequency(“tf-idf indexed”) statistic is calculated for selected nouns,reflecting how important a data item is to a data document given thespecific set of data documents 104; a coefficient may be computed basedon the data item count in the document and a data item count in the setof data documents 104. In some embodiments, the system 100 identifies apredetermined number of the highest tf-idf indexed and stemmed nouns perdocument, generating an aggregate complete list of selected nouns todefine document vectors (e.g., and as understood by one of ordinaryskill in the art, vectors indicating whether a particular data itemappears in a document) used in training the semantic map 106. In otherembodiments, functionality for preprocessing and vectorization of theset of data documents 104 generates a vector for each document in theset of data documents 104. In one of these embodiments, an identifierand an integer per data item on the list of selected nouns representeach document.

In one embodiment, the machine 102 provides the preprocessed documentsto a full-text search system 122. For example, the parser andpreprocessing module 110 may provide this functionality. In anotherembodiment, use of the full-text search system 122 enables interactiveselection of the documents. For example, the full-text search system 122may provide functionality allowing for retrieval of all documents, orsnippets of original documents, that contain a specific data item using,for example, literal exact matching. In still another embodiment, eachof the preprocessed documents (or snippets of preprocessed documents) isassociated with at least one of the following: a document identifier, asnippet identifier, a document title, the text of the document, a countof data items in the document, a length in bytes of the document, and aclassification identifier. In another embodiment, and as will bediscussed in further detail below, semantic map coordinate pairs areassigned to documents; such coordinate pairs may be associated with thepreprocessed documents in the full-text search system 122. In such anembodiment, the full-text search system 122 may provide functionalityfor receiving a single or compound data item and for returning thecoordinate pairs of all matching documents containing the received dataitem. Full-text search systems 122 include, without limitation,Lucene-based Systems (e.g., Apache SOLR distributed by The ApacheSoftware Foundation, Forest Hills, Md., and ELASTICSEARCH distributed byElasticsearch Global BV, Amsterdam, The Netherlands), open sourcesystems (Indri distributed by The Lemur Project through SourceForgeLemur Project, owned and operated by Slashdot Media, San Francisco,Calif., a Dice Holdings, Inc. company, New York, N.Y.; MNOGOSEARCHdistributed by Lavtech.Com Corp.; Sphinx distributed by SphinxTechnologies Inc.; Xapian distributed by the Xapian Project; Swish-edistributed by Swish-e.org; BaseX distributed by BaseX GmbH, Konstanz,Germany; DataparkSearch Engine distributed by www.dataparksearch.org;ApexKB distributed by SourceForge, owned and operated by Slashdot Media;Searchdaimon distributed by Searchdaimon AS, Oslo, Norway; and Zettairdistributed by RMIT University, Melbourne, Australia), and commercialsystems (Autonomy IDOL manufactured by Hewlett-Packard, Sunnyvale,Calif.; the COGITO product line manufactured by Expert System S.p.A. ofModena, Italy; Fast Search & Transfer manufactured by Microsoft, Inc. ofRedmond, Wash.; ATTIVIO manufactured by Attivio, Inc. of Newton, Mass.;BRS/Search manufactured by OpenText Corporation, Waterloo, Ontario,Canada; Perceptive Intelligent Capture (powered by Brainware)manufactured by Perceptive Software from Lexmark, Shawnee, Kans.; any ofthe products manufactured by Concept Searching, Inc. of McLean, Va.;COVEO manufactured by Coveo Solutions, Inc. of San Mateo, Calif.;Dieselpoint SEARCH manufactured by Dieselpoint, Inc. of Chicago, Ill.;DTSEARCH manufactured by dtSearch Company, Bethesda, Md.; Oracle EndecaInformation Discovery manufactured by Oracle Corporation, RedwoodShores, Calif.; products manufactured by Exalead, a subsidiary ofDassault Systemes of Paris, France; Inktomi search engines provided byYahoo!; ISYS Search now Perceptive Enterprise Search manufactured byPerceptive Software from Lexmark of Shawnee, Kans.; Locayta now ATTRAQTFREESTYLE MERCHANDISING manufactured by ATTRAQT, LTD. of London,England, UK; Lucid Imagination now LUCIDWORKS manufactured by LucidWorksof Redwood City, Calif.; MARKLOGIC manufactured by MarkLogicCorporation, San Carlos, Calif.; Mindbreeze line of productsmanufactured by Mindbreeze GmbH of Linz, Austria; Omniture now AdobeSiteCatalyst manufactured by Adobe Systems, Inc. of San Jose, Calif.;OpenText line of products manufactured by OpenText Corporation ofWaterloo, Ontario, Canada; PolySpot line of products manufactured byPolySpot S.A. of Paris, France; Thunderstone line of productsmanufactured by Thunderstone Software LLC of Cleveland, Ohio; andVivisimo now IBM Watson Explorer manufactured by IBM Corporation ofArmonk, N.Y.). Full-text search systems may also be referred to hereinas enterprise search systems.

In one embodiment, the reference map generator 106 accesses the documentvectors of the set of data documents 104 to distribute each of thedocuments across a two-dimensional metric space. In another embodiment,the reference map generator 106 accesses the preprocessed set of datadocuments 104 to distribute points representing each of the documentsacross the two-dimensional metric space. In still another embodiment,the distributed points are clustered. For example, the reference mapgenerator 106 may calculate a position of a point representing adocument based on semantic content of the document. The resultingdistribution represents the semantic universe of a specific set of datadocuments 104.

In one embodiment, the reference map generator 106 is trained using thedocument vectors of the preprocessed set of data documents 104. Inanother embodiment, the reference map generator 106 is trained using thedocument vectors of the set of data documents 104 (e.g., withoutpreprocessing). Users of the system 100 may use training processes wellunderstood by those skilled in the relevant arts to train the referencemap generator 106 with the set of data documents 104.

In one embodiment, the training process leads to two results. First, foreach document in a set of data documents 104, a pair of coordinates isidentified that positions the document on the semantic map 108; thecoordinates may be stored in the respective document entry within thefull-text search system 122. Second, a map of weights is generated thatallows the reference map generator 106 to position any new (unseen)document vector on the semantic map 108; after the training of thereference map generator 106, the document distribution may remainstatic. However, if the initial training set is large and descriptiveenough, adding new training documents can extend the vocabulary. Inorder to avoid the time consuming re-computation of the semantic map,new documents may be positioned on the map by transforming theirdocument vectors with the trained weights. The intended semantic map 108can be refined and improved by analyzing the distribution of the pointsrepresenting documents over the semantic map 108. If there are topicsthat are under- or over-represented, the set of data documents 104 canbe adapted accordingly and the semantic map 108 can then be recomputed.

Therefore, the method 200 includes clustering, by a reference mapgenerator executing on a computing device, in a two-dimensional metricspace, a set of data documents selected according to at least onecriterion, generating a semantic map. As discussed above and as will beunderstood by those of ordinary skill in the art, various techniques maybe applied to cluster the data documents; for example, and withoutlimitation, implementations may leverage generative topographic maps,growing self-organizing maps, elastic maps, neural gas, random mapping,latent semantic indexing, principal components analysis or any otherdimensionality reduction-based mapping method.

Referring now to FIG. 1B, a block diagram depicts one embodiment of asystem for generating a semantic map 108 for use in mapping data itemsto sparse distributed representations. As depicted in FIG. 1B, the setof data documents 104 received by the machine 102 may be referred to asa language definition corpus. Upon preprocessing of the set of datadocuments, the documents may be referred to as a reference map generatortraining corpus. The documents may also be referred to as a neuralnetwork training corpus. The reference map generator 106 accesses thereference map generator training corpus to generate as output a semanticmap 108 on which the set of data documents are positioned. The semanticmap 108 may extract the coordinates of each document. The semantic map108 may provide the coordinates to the full-text search system 122. Byway of non-limiting example, corpuses may include those based on anapplication (e.g., a web application for content creation andmanagement) allowing collaborative modification, extension, or deletionof its content and structure; such an application may be referred to asa “wiki” and the “Wikipedia” encyclopedia project supported and hostedby the Wikimedia Foundation of San Francisco, Calif., is one example ofsuch an application. Corpuses may also include knowledge bases of anykind or type.

As will be understood by those of ordinary skill in the art, any type orform of algorithm may be used to map high dimensional vectors into a lowdimensional space (e.g., the semantic map 108) by, for example,clustering the input vectors such that similar vectors are located closeto each other on the low dimensional space, resulting in a lowdimensional map that is topologically clustered. In some embodiments, asize of a quadratic semantic map defines the “semantic resolution” withwhich patterns of sparse distributed representations (SDRs) of dataitems will be computed, as will be discussed in further detail below.For example, a side-length of 128 corresponds to a descriptiveness of16K features per data item-SDR. In principle the size of the map can bechosen freely, considering that there are computational limits as biggerreference map generator sizes take longer to train and bigger SDRs takelonger to be compared or processed by any means. As another example, adata item SDR size of 128×128 has proven to be useful when applied on a“general English language” set of data documents 104.

Referring again to FIG. 2, the method 200 includes associating, by thesemantic map, a coordinate pair with each of the set of data documents(204). As discussed above, in populating the semantic map 108, thereference map generator 106 calculates a position of a point on thesemantic map 108, the point representing a document in the set of datadocuments 104. The semantic map 108 may then extract the coordinates ofthe point. In some embodiments, the semantic map 108 transmits theextracted coordinates to the full-text search system 122.

Referring now to FIG. 1C, a block diagram depicts one embodiment of asystem for generating a sparse distributed representation for each of aplurality of data items in the set of data documents 104. As shown inFIG. 1C, the representation generator 114 may transmit a query to thefull-text search system 122 and receive one or more data items matchingthe query. The representation generator 114 may generate sparsedistributed representations of data items retrieved from the full-textsearch system 122. In some embodiments, using data from a semantic map108 to generate the SDRs may be said to involve “folding” semanticinformation into generated sparse distributed representations (e.g.,sparsely populated vectors).

Referring back to FIG. 2, the method 200 includes generating, by aparser executing on the computing device, an enumeration of data itemsoccurring in the set of data documents (206). In one embodiment, theparser and preprocessing module 110 generates the enumeration of dataitems 112. In another embodiment, the parser and preprocessing module110 accesses the set of data documents 104 directly to generate theenumeration of data items 112. In still another embodiment, the parserand preprocessing module 110 accesses the full-text search system 122storing (as described above) a preprocessed version of the set of datadocuments 104. In another embodiment, the parser and preprocessingmodule 110 extends the enumeration of data items 112 to include not justthe data items explicitly included in the set of data documents 104 butcommon useful data item combinations; for example, the parser andpreprocessing module 110 may access frequent combinations of data items(such as “bad weather” or “electronic commerce”) retrieved from publiclyavailable collections.

In one embodiment, the parser and preprocessing module 110 delimits thedata items in the enumeration 112 using, for example, spaces, orpunctuation. In another embodiment, data items appearing in theenumeration 112 multiple times under different parts of speech tags aretreated as distinct (e.g., the data item “fish” will have a differentSDR if it is used as a noun than if it is used as a verb and so twoentries are included). In another embodiment, the parser andpreprocessing module 110 provides the enumeration of data items 112 tothe SDR database 120. In still another embodiment, the representationgenerator 114 will access the stored enumeration of data items 112 togenerate an SDR for each data item in the enumeration 112.

The method 200 includes determining, by a representation generatorexecuting on the computing device, for each data item in theenumeration, occurrence information including: (i) a number of datadocuments in which the data item occurs, (ii) a number of occurrences ofthe data item in each data document, and (iii) the coordinate pairassociated with each data document in which the data item occurs (208).In one embodiment, the representation generator 114 accesses thefull-text search system 122 to retrieve data stored in the full-textsearch system 122 by the semantic map 108 and the parser andpreprocessing module 110 and generates sparse distributedrepresentations for data items enumerated by the parser andpreprocessing module 110 using data from the semantic map 108.

In one embodiment, the representation generator 114 accesses thefull-text search system 122 to retrieve coordinate pairs for eachdocument that contain a particular string (e.g., words or numbers orcombinations of words and numbers). The representation generator 114 maycount the number of retrieved coordinate pairs to determine a number ofdocuments in which the data item occurs. In another embodiment, therepresentation generator 114 retrieves, from the full-text search system122, a vector representing each document that contains the string. Insuch an embodiment, the representation generator 114 determines a numberof set bits within the vector (e.g., the number of bits within thevector set to 1), which indicates how many times the data item occurredin a particular document. The representation generator 114 may add thenumber of set bits to determine the occurrence value.

The method 200 includes generating, by the representation generator, adistributed representation using the occurrence information (210). Therepresentation generator 114 may use well-known processes for generatingdistributed representation. In some embodiments, the distributedrepresentation may be used to determine a pattern representative ofsemantic contexts in which a data item in the set of data documents 104occurs; the spatial distribution of coordinate pairs in the patternreflects the semantic regions in the context of which the data itemoccurred. The representation generator 114 may generate a two-waymapping between a data item and its distributed representation. The SDRdatabase 120 may be referred to as a pattern dictionary with which thesystem 100 may identify data items based on distributed representationsand vice versa. Those of ordinary skill in the art will understand thatby using different sets of data documents 104 (e.g., selecting documentsof different types of subject matter, in different languages, based onvarying constraints) or originating from varying physical systems orfrom different medical analysis methods or from varying musical styles,the system 100 will generate different pattern dictionaries.

The method 200 includes receiving, by a sparsifying module executing onthe computing device, an identification of a maximum level of sparsity(212). In one embodiment, a human user provides the identification ofthe maximum level of sparsity. In another embodiment, the maximum levelof sparsity is set to a predefined threshold. In some embodiments, themaximum level of sparsity depends on a resolution of the semantic map108. In other embodiments, the maximum level of sparsity depends on atype of the reference map generator 106.

The method 200 includes reducing, by the sparsifying module, a totalnumber of set bits within the distributed representation based on themaximum level of sparsity to generate a sparse distributedrepresentation (SDR) having a normative fillgrade (214). In oneembodiment, the sparsifying module 116 sparsifies the distributedrepresentation by setting a count threshold (e.g., using the receivedidentification of the maximum level of sparsity) that leads to aspecific fillgrade of the final SDR 118. The sparsifying module 116therefore generates an SDR 118, which may be said to provide a binaryfingerprint of the semantic meaning or the semantic value of a data itemin the set of data documents 104; the SDR 118 may also be referred to asa semantic fingerprint. The sparsifying module 116 stores the SDR 118 inthe SDR database 120.

In generating an SDR, the system 100 populates a vector with 1s and 0s—1if a data document uses a data item, 0 if it doesn't, for example.Although a user may receive a graphical representation of the SDRshowing points on a map reflective of the semantic meaning of the dataitem (the graphical representation being referred to either as an SDR, asemantic fingerprint, or a pattern), and although the description hereinmay also refer to points and patterns, one of ordinary skill in the artwill understand that referring to “points” or “patterns” also refers tothe set bits within the SDR vector that are set—to the data structureunderlying any such graphical representation, which is optional.

In some embodiments, the representation generator 114 and thesparsifying module 116 may combine a plurality of data items into asingle SDR. For example, if a phrase, sentence, paragraph, or othercombination of data items needs to be converted into a single SDR thatreflects the “union property” of the individual SDRs, the system 100 mayconvert each individual data item into its SDR (by generatingdynamically or by retrieving the previously generated SDR) and use abinary OR operation to form a single compound SDR from the individualSDRs. Continuing with this example, the number of set bits is added forevery location within the compound SDR. In one embodiment, thesparsifying module 116 may proportionally reduce a total number of setbits using a threshold resulting in a normative fillgrade. In anotherembodiment, the sparsifying module 116 may apply a weighting scheme toreduce the total number of set bits, which may include evaluating anumber of bits surrounding a particular set bit instead of simplycounting the number of set bits per location in the SDR. Such a localityweighting scheme may favor bits that are part of clusters within the SDRand are therefore semantically more important than single isolated bits(e.g., with no set bits surrounding them).

In some embodiments, implementation of the methods and systems describedherein provides a system that does not simply generate a map thatclusters sets of data documents by context, but goes on to analyze thepositions on the map representing clustered data documents, determinewhich data documents include a particular data item based on theanalysis, and use the analysis to provide a specification for each dataitem in each data document. The sparse distributed representations ofthe data items are generated based on data retrieved from the semanticmap 108. The sparse distributed representations of the data items neednot be limited to use in training other machine learning methods, butmay be used to determine relationships between the data items (such as,for example, determining similarity between data items, ranking dataitems, or identifying data items that users did not previously know tobe similar for use in searching and analysis in a variety ofenvironments). In some embodiments, by transforming any piece ofinformation in an SDR using the methods and systems as described herein,any data item becomes “semantically grounded” (e.g., within its semanticuniverse) and therefore explicitly comparable and computable evenwithout using any machine learning, neural network, or corticalalgorithm.

Referring now to FIG. 3, a block diagram depicts one embodiment of asystem for performing operations using sparse distributedrepresentations of data items from data documents clustered on semanticmaps. In one embodiment, the system 300 includes functionality fordetermining semantic similarity between sparse distributedrepresentations. In another embodiment, the system 300 includesfunctionality for determining relevance ranking of data items convertedinto SDRs by matching against a reference data item converted into anSDR. In still another embodiment, the system 300 includes functionalityfor determining classifications of data items converted into SDRs bymatching against a reference text element converted into an SDR. Inanother embodiment, the system 300 includes functionality for performingtopic filtering of data items converted into SDRs by matching against areference data item converted into an SDR. In yet another embodiment,the system 300 includes functionality for performing keyword extractionfrom data items converted into SDRs.

In brief overview, the system 300 includes the elements and provides thefunctionality described above in connection with FIGS. 1A-1C (shown inFIG. 3 as the engine 101 and the SDR database 120). The system 300 alsoincludes a machine 102 a, a machine 102 b, a fingerprinting module 302,a similarity engine 304, a disambiguation module 306, a data item module308, and an expression engine 310. In one embodiment, the engine 101executes on the machine 102 a. In another embodiment, the fingerprintingmodule 302, the similarity engine 304, the disambiguation module 306,the data item module 308, and the expression engine 310 execute on themachine 102 b.

Referring now to FIG. 3, in connection with FIGS. 1A-1C and 2, thesystem 300 includes a fingerprinting module 302. In one embodiment, thefingerprinting module 302 includes the representation generator 114 andthe sparsifying module 116 described above in connection with FIGS.1A-1C and 2. In another embodiment, the fingerprinting module 302 formspart of the engine 101. In other embodiments, the fingerprinting module302 is implemented at least in part as a hardware module. In otherembodiments, the fingerprinting module 302 is implemented at least inpart as a software program. In still other embodiments, thefingerprinting module 302 executes on the machine 102. In someembodiments, the fingerprinting module 302 performs a postproductionprocess to transform a data item SDR into a semantic fingerprint (e.g.,via the sparsification process described herein) in real-time, with SDRsthat are not part of the SDR database 120 but that are generateddynamically (e.g., to create document semantic fingerprints from wordsemantic fingerprints); however, such postproduction processing isoptional. In other embodiments, the representation generator 114 may beaccessed directly in order to generate sparsified SDRs for data itemsthat do not yet have SDRs in the SDR database 120; in such anembodiment, the representation generator 114 may call the sparsifyingmodule 116 automatically and automatically generate a sparsified SDR.The terms “SDR” and “fingerprint” and “semantic fingerprint” are usedinterchangeably herein and may be used to refer both to SDRs that havebeen generated by the fingerprinting module 302 and to SDRs that aregenerated by the calling the representation generator 114 directly.

The system 300 includes a similarity engine 304. The similarity engine304 may provide functionality for computing distances between SDRs anddetermining a level of similarity. In other embodiments, the similarityengine 304 is implemented at least in part as a hardware module. Inother embodiments, the similarity engine 304 is implemented at least inpart as a software program. In still other embodiments, the similarityengine 304 executes on the machine 102 b.

The system 300 includes a disambiguation module 306. In one embodiment,the disambiguation module 306 identifies contextual sub-spaces embodiedwithin a single SDR of a data item. Therefore, the disambiguation module306 may allow users to better understand different semantic contexts ofa single data item. In some embodiments, the disambiguation module 306is implemented at least in part as a hardware module. In someembodiments, the disambiguation module 306 is implemented at least inpart as a software program. In other embodiments, the disambiguationmodule 306 executes on the machine 102 b.

The system 300 includes a data item module 308. In one embodiment, thedata item module 308 provides functionality for identifying the mostcharacteristic data items from a set of received data items—that is,data items whose SDRs have less than a threshold distance from an SDR ofthe received set of data items, as will be discussed in greater detailbelow. The data item module 308 may be used in conjunction with orinstead of a keyword extraction module 802 discussed below in connectionwith FIG. 8A. In some embodiments, the data item module 308 isimplemented at least in part as a hardware module. In some embodiments,the data item module 308 is implemented at least in part as a softwareprogram. In other embodiments, the data item module 308 executes on themachine 102 b.

The system 300 includes an expression engine 310. In one embodiment, aswill be discussed in greater detail below, the expression engine 310provides functionality for evaluating Boolean operators received withone or more data items from a user. Evaluating the Boolean operatorsprovides users with flexibility in requesting analysis of one or moredata items or combinations of data items. In some embodiments, theexpression engine 310 is implemented at least in part as a hardwaremodule. In some embodiments, the expression engine 310 is implemented atleast in part as a software program. In other embodiments, theexpression engine 310 executes on the machine 102 b.

Referring now to FIG. 4, a flow diagram depicts one embodiment of amethod for identifying a level of similarity between data items. Inbrief overview, the method 400 includes clustering, by a reference mapgenerator executing on a computing device, in a two-dimensional metricspace, a set of data documents selected according to at least onecriterion, generating a semantic map (402). The method 400 includesassociating, by the semantic map, a coordinate pair with each of the setof data documents (404). The method 400 includes generating, by a parserexecuting on the computing device, an enumeration of data itemsoccurring in the set of data documents (406). The method 400 includesdetermining, by a representation generator executing on the computingdevice, for each data item in the enumeration, occurrence informationincluding: (i) a number of data documents in which the data item occurs,(ii) a number of occurrences of the data item in each data document, and(iii) the coordinate pair associated with each data document in whichthe data item occurs (408). The method 400 includes generating, by therepresentation generator, a distributed representation using theoccurrence information (410). The method 400 includes receiving, by asparsifying module executing on the computing device, an identificationof a maximum level of sparsity (412). The method 400 includes reducing,by the sparsifying module, a total number of set bits within thedistributed representation based on the maximum level of sparsity togenerate a sparse distributed representation (SDR) having a normativefillgrade (414). The method 400 includes determining, by a similarityengine executing on the computing device, a distance between a first SDRof a first data item and a second SDR of a second data item (416). Themethod 400 includes providing, by the similarity engine, anidentification of a level of semantic similarity between the first dataitem and the second data item based upon the determined distance (418).

Referring to FIG. 4 in greater detail, and in connection with FIGS.1A-1C and 2-3, the method 400 includes clustering, by a reference mapgenerator executing on a computing device, in a two-dimensional metricspace, a set of data documents selected according to at least onecriterion, generating a semantic map (402). In one embodiment, theclustering occurs as described above in connection with FIG. 2 (202).

The method 400 includes associating, by the semantic map, a coordinatepair with each of the set of data documents (404). In one embodiment,the associating occurs as described above in connection with FIG. 2(204).

The method 400 includes generating, by a parser executing on thecomputing device, an enumeration of data items occurring in the set ofdata documents (406). In one embodiment, the generating occurs asdescribed above in connection with FIG. 2 (206).

The method 400 includes determining, by a representation generatorexecuting on the computing device, for each data item in theenumeration, occurrence information including: (i) a number of datadocuments in which the data item occurs, (ii) a number of occurrences ofthe data item in each data document, and (iii) the coordinate pairassociated with each data document in which the data item occurs (408).In one embodiment, the determining occurs as described above inconnection with FIG. 2 (208).

The method 400 includes generating, by the representation generator, adistributed representation using the occurrence information (410). Inone embodiment, the generating occurs as described above in connectionwith FIG. 2 (210).

The method 400 includes receiving, by a sparsifying module executing onthe computing device, an identification of a maximum level of sparsity(412). In one embodiment, the receiving occurs as described above inconnection with FIG. 2 (212).

The method 400 includes reducing, by the sparsifying module, a totalnumber of set bits within the distributed representation based on themaximum level of sparsity to generate a sparse distributedrepresentation (SDR) having a normative fillgrade (414). In oneembodiment, the reducing occurs as described above in connection withFIG. 2 (214).

The method 400 includes determining, by a similarity engine executing onthe computing device, a distance between a first SDR of a first dataitem and a second SDR of a second data item (416). In one embodiment,the similarity engine 304 computes the distance between at least twoSDRs. Distance measures may include, without limitation, Direct Overlap,Euclidian Distance (e.g., determining the ordinary distance between twopoints in an SDR in a similar manner as a human would measure with aruler), Jaccard Distance, and Cosine-similarity. The smaller thedistance between two SDRs, the greater the similarity and (with semanticfolding SDRs) a higher similarity indicates a higher semanticrelatedness of the data elements the SDRs represent. In one embodiment,the similarity engine 304 counts a number of bits that are set on boththe first SDR and the second SDR (e.g., points at which both SDRs areset to 1). In another embodiment, the similarity engine 304 identifies afirst point in the first SDR (e.g., an arbitrarily selected first bitthat is set to 1), finds the same point within the second SDR anddetermines the closest set bit in the second SDR. By determining whatthe closest set bit in the second SDR is to a set bit in the firstSDR—for each set bit in the first SDR—the similarity engine 304 is ableto calculate a sum of the distances at each point and divide by thenumber of points to determine the total distance. Those of ordinaryskill in the art will understand other mechanisms may be used todetermine distances between SDRs. In some embodiments, similarity is notan absolute measure but may vary depending on the different contextsthat a data item might have. In one of these embodiments, therefore, thesimilarity engine 304 also analyzes the topography of the overlapbetween the two SDRs. For example, the topology of the overlap may beused to add a weighting function to the similarity computation. Asanother example, similarity measures may be used.

The method 400 includes providing, by the similarity engine, anidentification of a level of semantic similarity between the first dataitem and the second data item data item based upon the determineddistance (418). The similarity engine 304 may determine that thedistance between the two SDRs exceeds a maximum threshold for similarityand thus the represented data items are not similar. Alternatively, thesimilarity engine 304 may determine that the distance between the twoSDRs does not exceed the maximum threshold and thus the represented dataitems are similar. The similarity engine 304 may identify the level ofsimilarity based upon a range, threshold, or other calculation. In oneembodiment, because SDRs actually represent the semantic meaning(expressed by a large number of semantic features) of a data item, it ispossible to determine the semantic closeness between two data items.

In some embodiments, the system 100 provides a user interface (notshown) with which users may enter data items and receive anidentification of the level of similarity. The user interface mayprovide this functionality to users directly accessing the machine 100.Alternatively, the user interface may provide this functionality tousers accessing the machine 100 across a computer network. By way ofexample, and without limitation, a user may enter a pair of data itemssuch as “music” and “apple” into the user interface; the similarityengine 304 receives the data items and generates the SDRs for the dataitems as described above in connection with FIGS. 1A-1C and 2.Continuing with this example, the similarity engine 304 may then comparethe two SDRs as described above. Although not required, the similarityengine 304 may provide a graphical representation of each of the SDRs tothe user via the user interface, allowing the user to visually reviewthe way in which each data item is semantically mapped (e.g., viewingthe points that are clustered in a semantic map representing a use ofthe data item in the reference collection used for training thereference map generator 106).

In some embodiments, the similarity engine 304 receives only one dataitem from a user. Referring now to FIG. 5, a flow diagram depicts oneembodiment of such a method. In brief overview, the method 500 includesclustering, by a reference map generator executing on a first computingdevice, in a two-dimensional metric space, a set of data documentsselected according to at least one criterion, generating a semantic map(502). The method 500 includes associating, by the semantic map, acoordinate pair with each of the set of data documents (504). The method500 includes generating, by a parser executing on the first computingdevice, an enumeration of data items occurring in the set of datadocuments (506). The method 500 includes determining, by arepresentation generator executing on the first computing device, foreach data item in the enumeration, occurrence information including: (i)a number of data documents in which the data item occurs, (ii) a numberof occurrences of the data item in each data document, and (iii) thecoordinate pair associated with each data document in which the dataitem occurs (508). The method 500 includes generating, by therepresentation generator, for each data item in the enumeration, adistributed representation using the occurrence information (510). Themethod 500 includes receiving, by a sparsifying module executing on thefirst computing device, an identification of a maximum level of sparsity(512). The method 500 includes reducing, by the sparsifying module, foreach distributed representation, a total number of set bits within thedistributed representation based on the maximum level of sparsity togenerate a sparse distributed representation (SDR) having a normativefillgrade (514). The method 500 includes storing, in an SDR database,each of the generated SDRs (516). The method 500 includes receiving, bya similarity engine executing on a second computing device, from a thirdcomputing device, a first data item (518). The method 500 includesdetermining, by the similarity engine, a distance between a first SDR ofthe first data item and a second SDR of a second data item retrievedfrom the SDR database (520). The method 500 includes providing, by thesimilarity engine, to the third computing device, an identification ofthe second data item and an identification of a level of semanticsimilarity between the first data item and the second data item, basedon the determined distance (522).

In some embodiments, (502)-(516) are performed as described above inconnection with FIG. 2 (202-214).

The method 500 includes receiving, by a similarity engine executing on asecond computing device, from a third computing device, a first dataitem (518). In one embodiment, the system 300 includes a user interface(not shown) with which a user may enter the first data item. In anotherembodiment, the fingerprinting module 302 generates an SDR of the firstdata item. In still another embodiment, the representation generator 114generates the SDR.

The method 500 includes determining, by the similarity engine, adistance between a first SDR of the first data item and a second SDR ofa second data item retrieved from the SDR database (520). In oneembodiment, the method 500 includes determining the distance between thefirst SDR of the first data item and the second SDR of the second dataitem as described above in connection with FIG. 4, (416). In someembodiments, the similarity engine 304 retrieves the second data itemfrom the SDR database 120. In one of these embodiments, the similarityengine 304 examines each entry in the SDR database 120 to determinewhether there is a level of similarity between the retrieved item andthe received first data item. In another of these embodiments, thesystem 300 implements current text indexing techniques and text searchlibraries to perform efficient indexing of a semantic fingerprint (i.e.,SDR) collection and to allow the similarity engine 304 to identify thesecond SDR of the second data item more efficiently than a “brute force”process such as iterating through each and every item in the database120.

The method 500 includes providing, by the similarity engine, to thethird computing device, an identification of the second data item and anidentification of a level of semantic similarity between the first dataitem and the second data item, based on the determined distance (522).In one embodiment, the similarity engine 304 provides theidentifications via the user interface. In another embodiment, thesimilarity engine 304 provides an identification of a level of semanticsimilarity between the first data item and the second data item basedupon the determined distance, as described above in connection with FIG.4, (418). In some embodiments, it will be understood, the similarityengine 304 retrieves a third SDR for a third data item from the SDRdatabase and repeats the process of determining a distance between thefirst SDR of the first data item and the third SDR of the third dataitem and providing an identification of a level of semantic similaritybetween the first and third data items, based on the determineddistance.

In one of these embodiments, the similarity engine 304 may return anenumeration of other data items that are most similar to the receiveddata item. By way of example, the similarity engine 304 may generate anSDR 118 for the received data item and then search the SDR database 120for other SDRs that are similar to the SDR 118. In other embodiments,the data item module 308 provides this functionality. By way of example,and without limitation, the similarity engine 304 (or the data itemmodule 308) may compare the SDR 118 for the received data item with eachof a plurality of SDRs in the SDR database 120 as described above andreturn an enumeration of data items that satisfy a requirement forsimilarity (e.g., having a distance between the data items that fallsbelow a predetermined threshold). In some embodiments, the similarityengine 304 returns the SDRs that are most similar to a particular SDR(as opposed to returning the data item itself).

In some embodiments, a method for receiving a data item (which may bereferred to as a keyword) and identifying similar data items performs asdescribed above in connection with FIG. 2 (202-214). In someembodiments, the data item module 308 provides this functionality. Inone of these embodiments, the method includes receiving a data item. Themethod may include receiving a request for most similar data items thatare not identical to the received data item. In another of theseembodiments, the method includes generating a first SDR for the receiveddata item. In still another of these embodiments, the method includesdetermining a distance between the first SDR and each SDR in the SDRdatabase 120. In yet another of these embodiments, the method includesproviding an enumeration of data items for which the distance between anSDR of an enumerated data item and the first SDR fall below a threshold.Alternatively, the method includes providing an enumeration of dataitems with a level of similarity between each data item and the receiveddata item above a threshold. In some embodiments, methods foridentifying similar data items provide functionality for receiving adata item or an SDR of a data item and generating an enumeration of SDRsordered by increasing distance (e.g., Euclidean distance). In one ofthese embodiments, the system 100 provides functionality for returningall contextual data items—that is, data items within the conceptualspace in which the submitted data item occurs.

The data item module 308 may return similar data items either to a userproviding the received data item or to another module or engine (e.g.,the disambiguation module 306).

In some embodiments, the system may generate an enumeration of similardata items and transmit the enumeration to a system for executingqueries, which may be either a system within the system 300 or athird-party search system. For example, a user may enter a data iteminto a user interface for executing queries (e.g., a search engine) andthe user interface may forward the data item to the query module 601;the query module 601 may automatically call components of the system(e.g., the similarity engine 304) to generate the enumeration of similardata items and provide the data items to the user interface forexecuting as queries in addition to the user's original query, therebyimproving the comprehensiveness of the user's search results. As anotherexample, and as will be discussed in further detail in connection withFIGS. 6A-6C, the system may generate the enumeration of similar dataitems, provide the data items directly to a third-party search system,and return the results of the expanded search to the user via the userinterface. Third-party search systems (which may also be referred toherein as enterprise search systems) may be any type or form; asindicated above in connection with the full-text search system 122, aside variety of such systems are available and may be enhanced using themethods and systems described herein.

Referring now to FIG. 6A, a block diagram depicts one embodiment of asystem 300 for expanding a query of a full-text search system. In briefoverview, the system 300 includes the elements and provides thefunctionality described above in connection with FIGS. 1A-1C and FIG. 3above. The system 300 includes a machine 102 d executing a query module601. The query module 601 executes a query expansion module 603, aranking module 605, and a query input processing module 607.

In one embodiment, the query module 601 receives query terms, directsthe generation of SDRs for the received terms, and directs theidentification of similar query terms. In another embodiment, the querymodule 601 is in communication with an enterprise search system providedby a third party. For example, the query module 601 may include one ormore interfaces (e.g., application programming interface) with which tocommunicate with the enterprise search system. In some embodiments, thequery module 601 is implemented at least in part as a software program.In other embodiments, the query module 601 is implemented at least inpart as a hardware module. In still other embodiments, the query module601 executes on the machine 102 d.

In one embodiment, the query input processing module 607 receives queryterms from a user of a client 102 c. In another embodiment, the queryinput processing module 607 identifies a type of query term (e.g.,individual word, group of words, sentence, paragraph, document, SDR, orother expression to be used in identifying similar terms). In someembodiments, the query input processing module 607 is implemented atleast in part as a software program. In other embodiments, the queryinput processing module 607 is implemented at least in part as ahardware module. In still other embodiments, the query input processingmodule 607 executes on the machine 102 d. In further embodiments, thequery module 601 is in communication with or provides the functionalityof the query input processing module 607.

In one embodiment, the query expansion module 603 receives query termsfrom a user of a client 102 c. In another embodiment, the queryexpansion module 603 receives query terms from the query inputprocessing module 607. In still another embodiment, the query expansionmodule 603 directs the generation of an SDR for a query term. In anotherembodiment, the query expansion module 603 directs the identification,by the similarity engine 304, of one or more terms that are similar tothe query term (based on a distance between the SDRs). In someembodiments, the query expansion module 603 is implemented at least inpart as a software program. In other embodiments, the query expansionmodule 603 is implemented at least in part as a hardware module. Instill other embodiments, the query expansion module 603 executes on themachine 102 d. In further embodiments, the query module 601 is incommunication with or provides the functionality of the query expansionmodule 603.

Referring now to FIG. 6B, a flow diagram depicts one embodiment of amethod 600 for expanding a query of a full-text search system. In briefoverview, the method 600 includes clustering, by a reference mapgenerator executing on a first computing device, in a two-dimensionalmetric space, a set of data documents selected according to at least onecriterion, generating a semantic map (602). The method 600 includesassociating, by the semantic map, a coordinate pair with each of the setof data documents (604). The method 600 includes generating, by a parserexecuting on the first computing device, an enumeration of termsoccurring in the set of data documents (606). The method 600 includesdetermining, by a representation generator executing on the firstcomputing device, for each term in the enumeration, occurrenceinformation including: (i) a number of data documents in which the termoccurs, (ii) a number of occurrences of the term in each data document,and (iii) the coordinate pair associated with each data document inwhich the term occurs (608). The method 600 includes generating, by therepresentation generator, a sparse distributed representation (SDR) foreach term in the enumeration, using the occurrence information for eachterm (610). The method 600 includes storing, in an SDR database, each ofthe generated SDRs (612). The method 600 includes receiving, by a queryexpansion module executing on a second computing device, from a thirdcomputing device, a first term (614). The method 600 includesdetermining, by a similarity engine executing on a fourth computingdevice, a level of semantic similarity between a first SDR of the firstterm and a second SDR of a second term retrieved from the SDR database(616). The method 600 includes transmitting, by the query expansionmodule, to a full-text search system, using the first term and thesecond term, a query for an identification of each of a set of documentscontaining at least one term similar to at least one of the first termand the second term (618). The method 600 includes transmitting, by thequery expansion module, to the third computing device, theidentification of each of the set of documents (620).

In some embodiments, (602)-(612) are performed as described above inconnection with FIG. 2 (202-214).

The method 600 includes receiving, by a query expansion module executingon a second computing device, from a third computing device, a firstterm (614). In one embodiment, the query expansion module 603 receivesthe first data item as described above in connection with FIG. 5 (516).In another embodiment, the query input processing module 607 receivesthe first term. In still another embodiment, the query input processingmodule 607 transmits the first term, with a request for generation of anSDR, to the fingerprinting module 302. In yet another embodiment, thequery input processing module 607 transmits the first term to the engine101 for generation of an SDR by the representation generator 114.

The method 600 includes determining, by a similarity engine executing ona fourth computing device, a level of semantic similarity between afirst SDR of the first term and a second SDR of a second term retrievedfrom the SDR database (616). In one embodiment, the similarity engine304 determines the level of semantic similarity as described above inconnection with FIG. 5 (520).

The method 600 includes transmitting, by the query expansion module, toa full-text search system, using the first term and the second term, aquery for an identification of each of a set of documents containing atleast one term similar to at least one of the first term and the secondterm (618). In some embodiments, the similarity engine 304 provides thesecond term to the query module 601. It will be understood that thesimilarity engine may provide a plurality of terms that have a level ofsimilarity to the first term that exceeds a similarity threshold. Inother embodiments, the query module 601 may include one or moreapplication programming interfaces with which to transmit queries,including one or more search terms, to the third-party enterprise searchsystem.

The method 600 includes transmitting, by the query expansion module, tothe third computing device, the identification of each of the set ofdocuments (620).

Referring now to FIG. 6C, a flow diagram depicts one embodiment of amethod 650 for expanding a query of a full-text search system. In briefoverview, the method 650 includes clustering, by a reference mapgenerator executing on a first computing device, in a two-dimensionalmetric space, a set of data documents selected according to at least onecriterion, generating a semantic map (652). The method 650 includesassociating, by the semantic map, a coordinate pair with each of the setof data documents (654). The method 600 includes generating, by a parserexecuting on the first computing device, an enumeration of termsoccurring in the set of data documents (656). The method 650 includesdetermining, by a representation generator executing on the firstcomputing device, for each term in the enumeration, occurrenceinformation including: (i) a number of data documents in which the termoccurs, (ii) a number of occurrences of the term in each data document,and (iii) the coordinate pair associated with each data document inwhich the term occurs (658). The method 650 includes generating, by therepresentation generator, a sparse distributed representation (SDR) foreach term in the enumeration, using the occurrence information for eachterm (660). The method 650 includes storing, in an SDR database, each ofthe generated SDRs (662). The method 650 includes receiving, by a queryexpansion module executing on a second computing device, from a thirdcomputing device, a first term (664). The method 650 includesdetermining, by a similarity engine executing on a fourth computingdevice, a level of semantic similarity between a first SDR of the firstterm and a second SDR of a second term retrieved from the SDR database(666). The method 650 includes transmitting, by the query expansionmodule, to the third computing device, the second term (668).

In one embodiment, (652)-(666) are performed as described above inconnection with (602-616). However, instead of providing the term orterms identified by the similarity engine directly to the enterprisesearch system, the method 650 includes transmitting, by the queryexpansion module, to the third computing device, the second term (668).In such a method, a user of the third computing device has the abilityto review or modify the second term before the query is transmitted tothe enterprise search system. In some embodiments, the user wantsadditional control over the query. In other embodiments, the userprefers to execute the queries herself. In further embodiments, the userwants the ability to modify a term identified by the system beforetransmission of the query. In still other embodiments, providing theidentified term to the user allows the system to request feedback fromthe user regarding the identified term. In one of these embodiments, forexample, the user may rate the accuracy of the similarity engine inidentifying the second term. In another of these embodiments, by way ofexample, the user provides an indication that the second term is a typeof term in which the user has a level of interest (e.g., the second termis a type the user is currently researching or developing an area ofexpertise).

In some embodiments, a method for evaluating at least one Booleanexpression includes receiving, by the expression engine 310, at leastone data item and at least one Boolean operator. The method includesperforming the functionality described above in connection with FIG. 2(202-214). In one embodiment, the expression engine 310 receives aplurality of data items that a user combined using Boolean operators andparentheses. For example, the user may submit a phrase such as “jaguarSUB porsche” and the expression engine 310 will evaluate the phrase andgenerate a modified version of an SDR for the expression. In anotherembodiment, therefore, the expression engine 310 generates a first SDR118 for a first data item in the received phrase. In still anotherembodiment, the expression engine 310 identifies the Boolean operatorwithin the received phrase (e.g., by determining that the second dataitem in a three-data item phrase is the Boolean operator or by comparingeach data item in the received phrase to an enumeration of Booleanoperators to determine whether the data item is a Boolean operator ornot). The expression engine 310 evaluates the identified Booleanoperator to determine how to modify the first data item. For example,the expression evaluator 310 may determine that a Boolean operator “SUB”is included in the received phrase; the expression engine 310 may thendetermine to generate a second SDR for a data item following the Booleanoperator (e.g., porsche, in the example phrase above) and generate athird SDR by removing the points from the first SDR that appear in thesecond SDR. The third SDR would then be the SDR of the first data item,not including the SDR of the second data item. Similarly, if theexpression engine 310 determined that the Boolean operator was “AND,”the expression engine 310 would generate a third SDR by only usingpoints in common to the first and the second SDR. Therefore, theexpression engine 310 accepts data items, compound data items, and SDRscombined using Boolean operators and parentheses and returns an SDR thatreflects the Boolean result of the formulated expression. The resultingmodified SDR may be returned to a user or provided to other engineswithin the system 200 (e.g., the similarity engine 304). As those ofordinary skill in the art will understand, Boolean operators include,without limitation, AND, OR, XOR, NOT, and SUB.

In some embodiments, a method for identifying a plurality ofsub-contexts of a data item includes receiving, by the disambiguationmodule 306, a data item. The method includes performing thefunctionality described above in connection with FIG. 2 (202-214). Inone embodiment, the method includes generating a first SDR for thereceived data item. In another embodiment, the method includesgenerating an enumeration of data items that have SDRs that are similarto the first SDR; for example, the method may include providing thefirst SDR to the similarity engine and requesting an enumeration ofsimilar SDRs as described above. In still another embodiment, the methodincludes analyzing one of the enumerated SDRs that is similar but notequal to the first SDR and removing from the first SDR the points (e.g.,set bits) that also appear in the enumerated SDR (e.g., via binarysubtraction) to generate a modified SDR. In another embodiment, themethod includes repeating the process of removing points that appear inboth the first SDR and the similar (but not identical) SDRs until themethod has removed from the first SDR all the points that appear in eachof the enumeration of similar SDRs. By way of example, upon receiving arequest for data items similar to the data item “apple,” the system mayreturn data items such as “macintosh,” and “iphone,” “operating system;”if a user provides the expression “apple SUB macintosh” and asks forsimilar data items from the remaining points, the system may return dataitems such as “fruit,” “plum,” “orange,” “banana.” Continuing with thisexample, if the user then provides the expression “apple SUB macintoshSUB fruit” and repeats the request for similar data items, the systemmay return data items such as “records,” “beatles,” and “pop music.” Insome embodiments, the method includes subtraction of the points of thesimilar SDRs from the largest clusters in the first SDR instead of fromthe entire SDR, providing a more optimized solution.

In some embodiments, as indicated above, data items may refer to itemsother than words. By way of example, the system 300 (e.g., thesimilarity engine 304) may generate SDRs for numbers, compare the SDRswith reference SDRs generated from other numbers and provide users withenumerations of similar data items. For example, and without limitation,the system 300 (e.g., the similarity engine 304) may generate an SDR forthe data item “100.1” and determine that the SDR has a similar patternto an SDR for a data item associated with a patient who was diagnosedwith infection triggered fever (e.g., in an embodiment in which a doctoror healthcare entity implements the methods and systems describedherein, data items generated based on physical characteristics of apatient, such as body temperature or any other characteristic, thesystem may store an association between an SDR for the data item (100.1)and an identification of the data item as a reference data item for apatient with a fever). Determining that the data items have similarpatterns provides functionality for identifying commonalities betweendynamically generated SDRs and reference SDRs, enabling users to betterunderstand the import of a particular data item. In some embodiments,therefore, the reference SDRs are linked to qualified diagnoses, makingit possible to match a new patient's SDR profile against diagnosedpatterns and deduct from it a mosaic of possible diagnoses for the newpatient. In one of these embodiments, by aggregating this collection ofpotential diagnoses, users may “see” where points (e.g., semanticfeatures of a data item) overlap and/or match. In such an embodiment,the most similar diagnosis to the new patient's SDR pattern is thepredicted diagnoses.

As another example, and without limitation, the set of data documents104 may include logs of captured flight data generated by airplanesensors (as opposed to, for example, encyclopedia entries on flight);the logs of captured data may include alphanumeric data items or may beprimarily numeric. In such an example, the system 100 may providefunctionality for generating SDRs of a variable (e.g., a variableassociated with any type of flight data) and compare the generated SDRwith a reference SDR (e.g., an SDR of a data item used as a referenceitem known to have a particular characteristic such as a fact about theflight during which the data item was generated, for example, that theflight had a particular level of altitude or a characterization of thealtitude such as too high or too low). As another example, the system100 may generate a first SDR for “500 (degrees)” and determine that thefirst SDR is similar to a second SDR for “28,000 (feet).” The system 100may then determine that the second SDR is a reference SDR for data itemsindicating a characteristic of the flight (e.g., too high, too low, toofast, etc.), and thus provide a user who started with a data item “500”with an understanding of the import of the data item.

In some embodiments, a method is provided for dividing a document intoportions (also referred to herein as slices) while respecting thetopical structure of the submitted text. In one embodiment, the dataitem module 308 receives a document to be divided into topical slices.In another embodiment, the data item module 308 identifies a location inthe document that has a different semantic fingerprint than a secondlocation and divides the document into two slices, one containing thefirst location and one containing the second. The method includesperforming the functionality described above in connection with FIG. 2(202-214). In one embodiment, the method includes generating an SDR 118for each sentence (e.g., strings delimited by periods) in the document.In another embodiment, the method includes comparing a first SDR 118 aof a first sentence with a second SDR 118 b of a second sentence. Forexample, the method may include transmitting the two SDRs to thesimilarity engine 304 for comparison. In still another embodiment, themethod includes inserting a break into the document after the firstsentence when the distance between the two SDRs exceeds a predeterminedthreshold. In another embodiment, the method includes determining not toinsert a break into the document when the distance between the two SDRsdoes not exceed the predetermined threshold. In still anotherembodiment, the method includes repeating the comparison between thesecond sentence and a subsequent sentence. In another embodiment, themethod includes iterating through the document, repeating comparisonsbetween sentences until reaching the end of the document. In yet anotherembodiment, the method includes using the inserted breaks to generateslices of the document (e.g., returning a section of the document upthrough a first inserted break as a first slice). In some embodiments,having a plurality of smaller slices is preferred over a document butarbitrarily dividing a document (e.g., by length or word count) may beinefficient or less useful than a topic-based division. In one of theseembodiments, by comparing the compound SDRs of the sentences, the system300 can determine where the topic of the document has changed creating alogical dividing point. In another of these embodiments, the system 300may provide a semantic fingerprint index in addition to a conventionalindex. Further examples of topic slicing are discussed in connectionwith FIGS. 7A-7B below.

Referring now to FIG. 7A, and in connection with FIG. 7B, a blockdiagram depicts one embodiment of a system 700 for providing topic-baseddocuments to a full-text search system. In brief overview, the system700 includes the elements and provides the functionality described abovein connection with FIGS. 1A-1C and FIG. 3 above. The system 700 furtherincludes a topic slicing module 702. In one embodiment, the topicslicing module 702 receives documents, directs the generation of SDRsfor the received documents, and directs the generation of sub-documentsin which sentences having less than a threshold level of similarity areplaced into different documents, or other data structures. In anotherembodiment, the topic slicing module 702 is in communication with anenterprise search system provided by a third party. In some embodiments,the topic slicing module 702 is implemented at least in part as asoftware program. In other embodiments, the topic slicing module 702 isimplemented at least in part as a hardware module. In still otherembodiments, the topic slicing module 702 executes on the machine 102 b.

Referring still to FIGS. 7A-B, a flow diagram depicts one embodiment ofa method 750 for providing topic-based documents to a full-text searchsystem. The method 750 includes clustering, by a reference map generatorexecuting on a first computing device, in a two-dimensional metricspace, a set of data documents selected according to at least onecriterion, generating a semantic map (752). The method 750 includesassociating, by the semantic map, a coordinate pair with each of the setof data documents (754). The method 750 includes generating, by a parserexecuting on the first computing device, an enumeration of termsoccurring in the set of data documents (756). The method 750 includesdetermining, by a representation generator executing on the firstcomputing device, for each term in the enumeration, occurrenceinformation including: (i) a number of data documents in which the termoccurs, (ii) a number of occurrences of the term in each data document,and (iii) the coordinate pair associated with each data document inwhich the term occurs (758). The method 750 includes generating, by therepresentation generator, a sparse distributed representation (SDR) foreach term in the enumeration, using the occurrence information (760).The method 750 includes storing, in an SDR database, each of thegenerated SDRs (762). The method 750 includes receiving, by a topicslicing module executing on a second computing device, from a thirdcomputing device associated with an enterprise search system, a secondset of documents (764). The method 750 includes generating, by therepresentation generator, a compound SDR for each sentence in the eachof the second set of documents (766). The method 750 includesdetermining, by a similarity engine executing on the second computingdevice, a distance between a first compound SDR of a first sentence anda second compound SDR of a second sentence (768). The method 750includes generating, by the topic slicing module, a second documentincluding the first sentence and a third document including the secondsentence, based on the determined distance (770). The method 750includes transmitting, by the topic slicing module, to the thirdcomputing device, the second document and the third document (772).

In one embodiment, (752)-(762) are performed as described above inconnection with FIG. 2, (202)-(214).

The method 750 includes receiving, by a topic slicing module executingon a second computing device, from a third computing device associatedwith an enterprise search system, a second set of documents (764). Inone embodiment, the topic slicing module 702 receives the second set ofdocuments for processing to create a version of the second set ofdocuments optimized for indexing by the enterprise search system, whichmay be a conventional search system. In another embodiment, the topicslicing module 702 receives the second set of documents for processingto create a version of the second set of documents optimized forindexing by a search system provided by the system 700, as will bedescribed in greater detail below in connection with FIGS. 9A-9B. Insome embodiments, the received second set of documents includes one ormore XML documents. For example, the third computing device may haveconverted one or more enterprise documents into XML documents forimproved indexing.

The method 750 includes generating, by the representation generator, acompound SDR for each sentence in each of the second set of documents(766). As discussed in connection with FIG. 2 above, if a phrase,sentence, paragraph, or other combination of data items needs to beconverted into a single SDR that reflects the “union property” of theindividual SDRs (e.g., the combination of the SDRs of each word in asentence), the system 100 may convert each individual data item into itsSDR (by generating dynamically or by retrieving the previously generatedSDR) and use a binary OR operation to form a single compound SDR fromthe individual SDRs; the result may be sparsified by the sparsifyingmodule 116.

The method 750 includes determining, by a similarity engine executing onthe second computing device, a distance between a first compound SDR ofa first sentence and a second compound SDR of a second sentence (768).In one embodiment, the similarity engine determines the distance asdescribed above in connection with FIG. 4 (416).

The method 750 includes generating, by the topic slicing module, asecond document including the first sentence and a third documentincluding the second sentence, based on the determined distance (770).The topic slicing module may determine that the distance determined bythe similarity engine exceeds a threshold for similarity and that thesecond sentence therefore relates to a different topic than the firstsentence and so should go into a different document (or other datastructure). In other embodiments, the similarity engine provides thetopic slicing module 702 with an identification of a level of similaritybetween the first sentence and the second sentence, based on thedetermined distance (as described above in connection with FIG. 4) andthe topic slicing module 702 determines that the level of similaritydoes not satisfy a threshold level of similarity and determines to putthe second sentence in a different document than the first sentence. Incontrast, in other embodiments, the topic slicing module 702 decidesthat the determined distance (and/or level of similarity) satisfies asimilarity threshold and that the first sentence and the second sentenceare topically similar and should remain together in a single document.

In still another embodiment, the method includes repeating thecomparison between the second sentence and a subsequent sentence. Inanother embodiment, the method includes iterating through the document,repeating comparisons between sentences until reaching the end of thedocument.

The method 750 includes transmitting, by the topic slicing module, tothe third computing device, the second document and the third document(772).

Referring now to FIG. 8B, and in connection with FIG. 8A, a flow diagramdepicts one embodiment of a method 850 for extracting keywords from textdocuments. The method 850 includes clustering in a two-dimensionalmetric space, by a reference map generator executing on a firstcomputing device, a set of data documents selected according to at leastone criterion, generating a semantic map (852). The method 850 includesassociating, by the semantic map, a coordinate pair with each of the setof data documents (854). The method 850 includes generating, by a parserexecuting on the first computing device, an enumeration of termsoccurring in the set of data documents (856). The method 850 includesdetermining, by a representation generator executing on the firstcomputing device, for each term in the enumeration, occurrenceinformation including: (i) a number of data documents in which the termoccurs, (ii) a number of occurrences of the term in each data document,and (iii) the coordinate pair associated with each data document inwhich the term occurs (858). The method 850 includes generating, by therepresentation generator, a sparse distributed representation (SDR) foreach term in the enumeration, using the occurrence information (860).The method 850 includes storing, in an SDR database, each of thegenerated SDRs (862). The method 850 includes receiving, by a keywordextraction module executing on a second computing device, from a thirdcomputing device associated with a full-text search system, a documentfrom a second set of documents (864). The method 850 includesgenerating, by the representation generator, at least one SDR for eachterm in the received document (866). The method 850 includes generating,by the representation generator, a compound SDR for the receiveddocument, based on the generated at least one SDR (868). The method 850includes selecting, by the keyword extraction module, a plurality ofterm SDRs that, when compounded, create a compound SDR that has a levelof semantic similarity to the compound SDR for the document, the levelof semantic similarity satisfying a threshold (870). The method 850includes modifying, by the keyword extraction module, a keyword field ofthe received document to include the plurality of terms (872). Themethod 850 includes transmitting, by the keyword extraction module, tothe third computing device, the modified document (874).

In one embodiment, (852)-(862) are performed as described above inconnection with FIG. 2, (202)-(214).

In one embodiment, the system 800 includes the elements and provides thefunctionality described above in connection with FIGS. 1A-1C and FIG. 3above. The system 800 further includes a keyword extraction module 802.In one embodiment, the keyword extraction module 802 receives documents,directs the generation of SDRs for the received documents, identifieskeywords for the received documents, and modifies the received documentsto include the identified keywords. In another embodiment, the keywordextraction module 802 is in communication with an enterprise searchsystem provided by a third party. In some embodiments, the keywordextraction module 802 is implemented at least in part as a softwareprogram. In other embodiments, the keyword extraction module 802 isimplemented at least in part as a hardware module. In still otherembodiments, the keyword extraction module 802 executes on the machine102 b.

The method 850 includes receiving, by a keyword extraction moduleexecuting on a second computing device, from a third computing deviceassociated with a full-text search system, a document from a second setof documents (864). In one embodiment, the keyword extraction module 802receives the documents as described at FIG. 7 (764), in connection withthe topic slicing module 702.

The method 850 includes generating, by the representation generator, atleast one SDR for each term in the received document (866). In oneembodiment, the keyword extraction module 802 transmits each term in thereceived document to the representation generator 114 to generate the atleast one SDR. In another embodiment, the keyword extraction module 802transmits each term in the received document to the fingerprintingmodule 302 for generation of the at least one SDR.

In some embodiments, the keyword extraction module 802 transmits thedocument to the fingerprinting module 302 with a request for generationof compound SDRs for each sentence in the document. In otherembodiments, the keyword extraction module 802 transmits the document tothe representation generator 114 with a request for generation ofcompound SDRs for each sentence in the document.

The method 850 includes generating, by the representation generator, acompound SDR for the document (868). In one embodiment, the keywordextraction module 802 requests generation of the compound SDR from therepresentation generator 114. In another embodiment, the keywordextraction module 802 requests generation of the compound SDR from thefingerprinting module 302.

The method 850 includes selecting, by the keyword extraction module, aplurality of term SDRs that, when compounded, create a compound SDR thathas a level of semantic similarity to the compound SDR for the document,the level of semantic similarity satisfying a threshold (870). In oneembodiment, the keyword extraction module 802 directs the similarityengine 304 to compare the compound SDR for the document with the SDRsfor a plurality of terms (“term SDRs”) and to generate an identificationof a level of similarity between the plurality of terms and the documentitself. In some embodiments, the keyword extraction module 802identifies the plurality of terms that satisfies the threshold by havingthe similarity engine iterate through combinations of term SDRs,generate comparisons with the compound SDR for the document, and returnan enumeration of a level of semantic similarity between the documentand each combination of terms. In another of these embodiments, thekeyword extraction module 302 identifies a plurality of terms having alevel of semantic similarity to the document that satisfies thethreshold and that also contains the least number of terms possible.

The method 850 includes modifying, by the keyword extraction module, akeyword field of the received document to include the plurality of terms(872). As indicated above, the received document may be a structureddocument, such as an XML document, and may have a section within whichthe keyword extraction module 802 may insert the plurality of terms.

The method 850 includes transmitting, by the keyword extraction module,to the third computing device, the modified document (874).

As described above, enterprise search systems may includeimplementations of conventional search systems, including thosedescribed in connection with the full-text search system 122 describedabove (e.g., Lucene-based systems, open source systems such as Xapian,commercial systems such as Autonomy IDOL or COGITO, and the othersystems listed in detail above). The phrases “enterprise search system”and “full-text search system” may be used interchangeably herein. Themethods and systems described in FIGS. 6-8 describe enhancements to suchenterprise systems; that is, by implementing the methods and systemsdescribed herein, an entity making such an enterprise system availablemay enhance the available functionality—making indexing more efficientby adding keywords, expanding query terms for users and automaticallyproviding them to the existing system, etc. However, entities makingsearch systems available to their users may wish to go further thanenhancing certain aspects of their existing systems by replacing thesystems entirely, or seeking to implement an improved search system inthe first instance. In some embodiments, therefore, an improved searchsystem is provided.

Referring now to FIG. 9A, a block diagram depicts one embodiment of asystem 900 for implementing a full-text search system 902. In oneembodiment, the system 900 includes the functionality described above inconnection with FIGS. 1A-1C, 3, 6A, 7A, and 8A. The search system 902includes the query module 601, which may be provided as described abovein connection with FIGS. 6A-6B. The search system 902 includes adocument fingerprint index 920; the document fingerprint index 920 maybe a version of the SDR database 120. The document fingerprint index 920may also include metadata (e.g., tags). The search system 902 mayinclude a document similarity engine 304 b; for example, the documentsimilarity engine 304 b may be a copy of the similarity engine 304 thatis refined over time for working with the search system 902. The searchsystem 902 includes an indexer 910, which may be provided as either ahardware module or a software module.

Referring now to FIG. 9B, and in connection with FIG. 9A, a method 950includes clustering in a two-dimensional metric space, by a referencemap generator executing on a first computing device, a set of datadocuments selected according to at least one criterion, generating asemantic map (952). The method 950 includes associating, by the semanticmap, a coordinate pair with each of the set of data documents (954). Themethod 950 includes generating, by a parser executing on the firstcomputing device, an enumeration of terms occurring in the set of datadocuments (956). The method 950 includes determining, by arepresentation generator executing on the first computing device, foreach term in the enumeration, occurrence information including: (i) anumber of data documents in which the term occurs, (ii) a number ofoccurrences of the term in each data document, and (iii) the coordinatepair associated with each data document in which the term occurs (958).The method 950 includes generating, by the representation generator, asparse distributed representation (SDR) for each term in theenumeration, using the occurrence information (960). The method 950includes storing, in an SDR database, each of the generated SDRs (962).The method 950 includes receiving, by a full-text search systemexecuting on a second computing device, a second set of documents (964).The method 950 includes generating, by the representation generator, atleast one SDR for each document in the second set of documents (966).The method 950 includes storing, by an indexer in the full-text searchsystem, each generated SDR in a document fingerprint index (968). Themethod 950 includes receiving, by a query module in the search system,from a third computing device, at least one search term (970). Themethod 950 includes querying, by the query module, the documentfingerprint index, for at least one term in the document fingerprintindex having an SDR similar to an SDR of the received at least onesearch term (972). The method 950 includes providing, by the querymodule, to the third computing device, a result of the query (974).

The method 950 includes clustering in a two-dimensional metric space, bya reference map generator executing on a first computing device, a setof data documents selected according to at least one criterion,generating a semantic map (952). In some embodiments, the set of datadocuments are selected and the clustering occurs as described above inconnection with FIG. 2 (202). As indicated above in connection withFIGS. 1-2, in initializing a system for use with the methods and systemsdescribed herein, a training process occurs. As described above, thereference map generator 106 is trained using at least one set of datadocuments (more specifically, using the document vectors of eachdocument in the set of data documents). As was also discussed above, thesemantic resolution of a set of documents refers to how many positionsare available based on the training data, which in some aspects reflectsthe nature of the training data (colloquially, this might be referred toas how much “real estate” is available on the map). To increase thesemantic resolution, different or additional training documents may beused. There are, therefore, several different approaches to training thereference map generator 106. In one embodiment, a generic trainingcorpus may be used when generating SDRs for each term received (e.g.,terms within enterprise documents); one advantage to such an approach isthat the corpus has likely been selected to satisfy one or more trainingcriteria but a disadvantage is that the corpus may or may not havesufficient words to support a specialized enterprise corpus (e.g., ahighly technical corpus including a number of terms that have particularmeanings within a specialty or practice). In another embodiment,therefore, a set of enterprise documents may be used as the trainingcorpus; one advantage to this approach is that the documents used fortraining will include any highly technical or otherwise specializedterms common within the enterprise but a disadvantage is that theenterprise documents may not satisfy the training criteria (e.g., theremay not be enough documents, they may be of insufficient length ordiversity, etc.). In still another embodiment, a generic training corpusand an enterprise corpus are combined for training purposes. In yetanother embodiment, a special set of technical documents is identifiedand processed for use as a training corpus; for example, these documentsmay include key medical treatises, engineering specifications, or otherkey reference materials in specialties relevant to the enterprisedocuments that will be used. By way of example, a reference corpus maybe processed and used for training and then the resulting engine 101 mayuse the trained database, separately licensed to enterprises seeking toimplement the methods and systems described herein. These embodimentsare equally applicable to the embodiments discussed in connection withFIGS. 6-8 as to those with FIGS. 9A-B.

Continuing with FIG. 9B, in some embodiments (954)-(962) are performedas described above in connection with FIGS. 1-2.

The method 950 includes receiving, by a full-text search systemexecuting on a second computing device, a second set of documents (964).In one embodiment, the second set of documents includes enterprisedocuments (e.g., documents generated by, maintained by, accessed by, orotherwise associated with an enterprise seeking to implement thefull-text search system 902). In another embodiment, the search system902 makes one or more enterprise documents searchable. To do so, thesearch system 902 indexes the one or more enterprise documents. In oneembodiment, the search system 902 directs the preprocessing of theenterprise documents (e.g., by having the topic slicing module 702and/or the keyword extraction module 802 process the documents asdescribed above in connection with FIGS. 7B and 8B). In anotherembodiment, the search system 902 directs the generation of an SDR foreach of the documents based on the training corpus (as described abovein connection with FIGS. 1-2). In still another embodiment, havinggenerated SDRs for each document, the search system 902 has enabled asearch process wherein a query term is received (e.g., by the queryinput processing module 607), an SDR is generated for the query term andthe query SDR is compared to a indexed SDRs.

The method 950 includes generating, by the representation generator, atleast one SDR for each document in the second set of documents (966). Inone embodiment, the search system 902 includes functionality fortransmitting the documents to the fingerprinting module 302 forgeneration of the at least one SDR. In another embodiment, the searchsystem 902 includes functionality for transmitting the documents to therepresentation generator 114 for generation of the at least one SDR. Theat least one SDR may include, by way of example, and without limitation,an SDR for each term in the document, a compound SDR for subsections ofthe document (e.g., sentences or paragraphs), and a compound SDR for thedocument itself.

The method 950 includes storing, by an indexer in the full-text searchsystem, each generated SDR in a document fingerprint index (968). In oneembodiment, the generated SDRs are stored in the document fingerprintindex 920 in a substantially similar manner as the manner in which SDRswere stored in the SDR database 120, discussed above.

The method 950 includes receiving, by a query module in the searchsystem, from a third computing device, at least one search term (970).In one embodiment, the query module receives the search term asdescribed above in connection with FIGS. 6A-6B.

The method 950 includes querying, by the query module, the documentfingerprint index, for at least one term in the document fingerprintindex having an SDR similar to an SDR of the received at least onesearch term (972). In one embodiment, the query module 601 queries thedocument fingerprint index 920. In another embodiment, in which thesystem 900 includes a document similarity engine 304 b, the query module601 directs the document similarity engine 304 b to identify the SDR ofthe at least one term in the document fingerprint index 920. In stillanother embodiment, the query module 601 directs the similarity engine304 executing on the machine 102 b to identify the term. In otherembodiments, the query module 601 executes the search as described abovein connection with FIGS. 6A-6B, although instead of sending the query toan external enterprise search system, the query module 601 sends thequery to components within the system 900.

The method 950 includes providing, by the query module, to the thirdcomputing device, a result of the query (974). In some embodiments, inwhich there is more than one result (e.g., more than one similar term),the query module 601 first ranks the results or directs another moduleto rank the results. Ranking may implement conventional rankingtechniques. Alternatively, ranking may include execution of the methodsdescribed in connection with FIGS. 11A-B below.

In some embodiments, the full-text search system 902 provides a userinterface (not shown) with which a user may provide feedback on thequery results. In one of these embodiments, the user interface includesa user interface element with which the user may specify whether theresult was useful. In another of these embodiments, the user interfaceincludes a user interface element with which the user may provide aninstruction to the query module 601 to execute a new search using one ofthe query results. In still another of these embodiments, the userinterface includes a user interface element with which the user mayspecify that they have an interest in a topic related to one of thequery results and wish to store an identifier of the query result and/orthe related topic for future reference by either the user or the system900.

In one embodiment, a system may provide functionality for monitoring thetypes of searches a user executes and developing a profile for the userbased on analysis of the SDRs of the search terms the user provided. Insuch an embodiment, the profile may identify a level of expertise of theuser and may be provided to other users.

Referring now to FIGS. 10A and 10B, block diagrams depict embodiments ofsystems for matching user expertise with requests for user expertise,based on previous search results. FIG. 1 OA depicts an embodiment inwhich functionality for developing user expertise profiles (e.g., userexpertise profile module 1010) is provided in conjunction with aconventional full-text search system. FIG. 10B depicts an embodiment inwhich functionality for developing user expertise profiles (e.g., userexpertise profile module 1010) is provided in conjunction with thefull-text search system 902. Each of the modules depicted in FIGS. 10A-Bmay be provided as either hardware modules or software modules.

Referring now to FIG. 10C, a flow diagram depicts an embodiment of amethod 1050 for matching user expertise with requests for userexpertise, based on previous search results. The method 1050 includesclustering in a two-dimensional metric space, by a reference mapgenerator executing on a first computing device, a set of data documentsselected according to at least one criterion, generating a semantic map(1052). The method 1050 includes associating, by the semantic map, acoordinate pair with each of the set of data documents (1054). Themethod 1050 includes generating, by a parser executing on the firstcomputing device, an enumeration of terms occurring in the set of datadocuments (1056). The method 1050 includes determining, by arepresentation generator executing on the first computing device, foreach term in the enumeration, occurrence information including: (i) anumber of data documents in which the term occurs, (ii) a number ofoccurrences of the term in each data document, and (iii) the coordinatepair associated with each data document in which the term occurs (1058).The method 1050 includes generating, by the representation generator, asparse distributed representation (SDR) for each term in theenumeration, using the occurrence information (1060). The method 1050includes storing each of the generated SDRs in an SDR database (1062).The method 1050 includes receiving, by a query module executing on asecond computing device, from a third computing device, at least oneterm (1064). The method 1050 includes storing, by a user expertiseprofile module executing on the second computing device, an identifierof a user of the third computing device and the at least one term(1066). The method 1050 includes generating, by the representationgenerator, an SDR of the least one term (1068). The method 1050 includesreceiving, by the user expertise profile module, from a fourth computingdevice, a second term and a request for an identification of a user whois associated with a similar term (1070). The method 1050 includesidentifying, by a similarity engine, a level of semantic similaritybetween the SDR of the at least one term and an SDR of the second term(1072). The method 1050 includes providing, by the user expertiseprofile module, to the fourth computing device, the identifier of theuser of the third computing device (1074).

In one embodiment, (1052)-(1062) are performed as described above inconnection with FIG. 2, (202)-(214).

The method 1050 includes receiving, by a query module executing on asecond computing device, from a third computing device, at least oneterm (1064). In one embodiment, the query module 601 receives the atleast one term and executes the query as described above in connectionwith FIGS. 6A-C and 9A-B.

The method 1050 includes storing, by a user expertise profile moduleexecuting on the second computing device, an identifier of a user of thethird computing device and the at least one term (1066). In oneembodiment, the user profile module 1002 receives the identifier of theuser and the at least one term from the query input processing module607. In another embodiment, the user expertise profile module 1010receives the identifier of the user and the at least one term from thequery input processing module 607. In still another embodiment, the userexpertise profile module 1010 stores the identifier of the user and theat least one term in a database. For example, the user expertise profilemodule 1010 stores the identifier of the user and the at least one termin the user expertise SDR database 1012 (e.g., with an SDR of the atleast one term). In some embodiments, the method includes loggingqueries that are received from users with user identifiers and SDRs foreach query term(s). In some embodiments, the user profile module 1002also includes functionality for receiving an identification of searchresults that the querying user indicated were relevant or otherwise ofinterest to the querying user.

The method 1050 includes generating, by the representation generator, anSDR of the least one term (1068). In one embodiment, the user expertiseprofile module 1010 transmits the at least one data item to thefingerprinting module 302 for generation of the SDR. In anotherembodiment, the user expertise profile module 1010 transmits the atleast one term to the representation generator 114 for generation of theSDR.

In some embodiments, the user expertise profile module 1010 receives aplurality of data items as the user continues to make queries over time.In one of these embodiments, the user expertise profile module 101directs the generation of a compound SDR that combines an SDR of a firstquery term with an SDR of a second query term; the resulting compoundSDR more accurately reflects the types of queries that the user makesand the more term SDRs that can be added to the compound SDR over time,the more accurately the compound SDR will reflect an area of expertiseof the user.

The method 1050 includes receiving, by the user expertise profilemodule, from a fourth computing device, a second term and a request foran identification of a user associated with a similar term (1070). Insome embodiments, the request for the identification of the userassociated with a similar data item is explicit. In other embodiments,the user expertise profile module 1010 automatically provides theidentification as a service to the user of the fourth computing device.By way of example, a user of the fourth computing device performing asearch for documents similar to query terms in a white paper the user isauthoring may request (or be provided with an option to receive) anidentification of other users who have developed an expertise in topicssimilar to the chosen query terms. By way of example, this functionalityallows users to identify those who have developed an expertise in aparticular topic, regardless of whether that expertise is part of theirofficial title, job description, or role, making information readilyavailable that was previously difficult to discern based only onofficial data or word of mouth or a personal connection. Since multipleareas of expertise (e.g., multiple SDRs based on one or more queryterms) may be associated with a single user, information is availableabout primary as well as secondary areas of expertise; for example,although an individual may officially focus on a first area of research,the individual may perform a series of queries over the course of a weekas they research a potential extension of their work into a second areaof research and the expertise gained in even that limited period of timemay be useful to another user. As another example, an individual seekingto build a team or structure (or restructure) an organization based onactual areas of interest may leverage the functionality of the userexpertise profile module 1010 to identify users who have expertiserelevant to the needs of the individual.

The method 1050 includes identifying, by a similarity engine, a level ofsemantic similarity between the SDR of the at least one term and an SDRof the second term (1072). In one embodiment, the similarity engine 304executes on the second machine 102 b. In another embodiment, thesimilarity engine 304 is provided by and executes within a search system902. Having received the query term from the user seeking to identify anindividual having an area of expertise, the user expertise profilemodule 1010 may direct the similarity engine 304 to identify other usersfrom the user expertise SDR database 1012 that satisfy the request.

The method 1050 includes providing, by the user expertise profilemodule, to the fourth computing device, the identifier of the user ofthe third computing device (1074).

In some embodiments, a user of the methods and systems described hereinmay provide an identification of a preference regarding query terms. Byway of example, a first user seeking to do a search on a query term maybe interested in documents that relate to legal aspects of the queryterm—for example, uses of the query term or terms like it in courtcases, patent applications, published licenses, or other legaldocuments—while a second user seeking to do a search on the same queryterm may be interested in documents that relate to scientific aspects ofthe query term—for example, uses of the query term or of terms like itin white papers, research publications, grant applications or otherscientific documents. In some embodiments, the systems described hereinprovide functionality for identifying such preferences and rankingsearch results according to which results are closest (based on SDRanalyses) to the type of document preferred by the searcher.

Referring back to FIGS. 10A and 10B, block diagrams depict embodimentsof systems for semantic ranking of query results received from anenterprise search system based on user preferences. FIG. 1 OA depicts anembodiment in which functionality for semantic ranking is provided inconjunction with results from a conventional enterprise search system.FIG. 10B depicts an embodiment in which functionality for semanticranking is provided in conjunction with results from a search system902.

Referring now to FIG. 10D, a flow diagram depicts one embodiment of amethod 1080 for user profile-based semantic ranking of query resultsreceived from a full-text search system. The method 1080 includesclustering in a two-dimensional metric space, by a reference mapgenerator executing on a first computing device, a set of data documentsselected according to at least one criterion, generating a semantic map(1081). The method 1080 includes associating, by the semantic map, acoordinate pair with each of the set of data documents (1082). Themethod 1080 includes generating, by a parser executing on the firstcomputing device, an enumeration of terms occurring in the set of datadocuments (1083). The method 1080 includes determining, by arepresentation generator executing on the first computing device, foreach term in the enumeration, occurrence information including: (i) anumber of data documents in which the term occurs, (ii) a number ofoccurrences of the term in each data document, and (iii) the coordinatepair associated with each data document in which the term occurs (1084).The method 1080 includes generating, by the representation generator, asparse distributed representation (SDR) for each term in theenumeration, using the occurrence information (1085). The method 1080includes storing each of the generated SDRs in an SDR database (1086).The method 1080 includes receiving, by a query module executing on asecond computing device, from a third computing device, a first term anda plurality of preference documents (1087). The method 1080 includesgenerating, by the representation generator, a compound SDR using theplurality of preference documents (1088). The method 1080 includestransmitting, by the query module, to a full-text search system, a queryfor an identification of each of a set of results documents similar tothe first term (1089). The method 1080 includes generating, by therepresentation generator, an SDR for each of the documents identified inthe set of results documents (1090). The method 1080 includesdetermining, by a similarity engine, a level of semantic similaritybetween each SDR generated for each of the set of results documents andthe compound SDR (1091). The method 1080 includes modifying, by aranking module executing on the second computing device, an order of atleast one document in the set of results documents, based on thedetermined level of semantic similarity (1092). The method 1080 includesproviding, by the query module, to the third computing device, theidentification of each of the set of results documents in the modifiedorder (1093).

In one embodiment (1081)-(1086) are performed as described above inconnection with FIG. 2, (202)-(214).

The method 1080 includes receiving, by a query module executing on asecond computing device, from a third computing device, a first term anda plurality of preference documents (1087). In one embodiment, the queryinput processing module 607 receives the first term as described abovein connection with FIGS. 6A-B and 9A-B. In another embodiment, the queryinput processing module 607 provides a user interface element (notshown) allowing a user of the third computing device to provide (e.g.,upload) one or more preference documents. Preference documents may beany type or form of data structure including one or more data itemsrepresentative of a type of document the searching user is interestedin. By way of example, a scientific researcher could provide a number ofresearch documents that reflect the style and/or content of the type ofdocuments the scientific researcher would consider relevant orpreferable given her search objectives. As another example, a lawyercould provide a number of legal documents that reflect the style and/orcontent of the type of documents the lawyer would consider relevant orpreferable given her search objectives. Furthermore, the system mayprovide functionality allowing a user to provide different sets ofpreference documents with different searches, allowing the user tocreate different preference profiles for use with different searches atdifferent times—for example, a different preference profile may berelevant for a scientific search focused on a first topic of researchthan would be relevant for a scientific search focused on a second,different topic.

The method 1080 includes generating, by the representation generator, acompound SDR using the plurality of preference documents (1088). In oneembodiment, the user preference module 1004 directs the generation ofthe compound SDR. For example, the user preference module 1004 maytransmit the preference documents to the fingerprinting module 302 forgeneration of the compound SDR. As another example, the user preferencemodule 1004 may transmit the preference documents to the representationgenerator 114 for generation of the compound SDR. The compound SDR thatcombines the SDRs of individual preference documents may be generated inthe same way that compound SDRs of individual documents are generatedfrom term SDRs. The user preference module 1004 may store the generatedcompound SDR in the user preference SDR database 1006.

The method 1080 includes transmitting, by the query module, to afull-text search system, a query for an identification of each of a setof results documents similar to the first term (1089). The query module601 may transmit the query to an external enterprise search system asdescribed in connection with FIGS. 6A-B. Alternatively, the query module601 may transmit the query to a search system 902 as described above inconnection with FIGS. 9A-B.

The method 1080 includes generating, by the representation generator, anSDR for each of documents identified in the set of results documents(1090). In one embodiment, the user preference module 1004 receives theset of results documents from the search system (either the searchsystem 902 or the third-party enterprise search system). In anotherembodiment, the user preference module 1004 directs the similarityengine 304 to generate the SDRs for each of the received resultsdocuments.

The method 1080 includes determining, by a similarity engine, a level ofsemantic similarity between each SDR generated for each of the set ofresults documents and the compound SDR (1091). In one embodiment, thesimilarity engine executes on the second machine 102 b. In anotherembodiment, the similarity engine is provided by and executes within asearch system 902. In one embodiment, the user preference module 1004directs the similarity engine 304 to identify the level of similarity.In another embodiment, the user preference module 1004 receives thelevel of similarity from the similarity engine 304.

The method 1080 includes modifying, by a ranking module executing on thesecond computing device, an order of at least one document in the set ofresults documents, based on the determined level of semantic similarity(1092). In one embodiment, by way of example and without limitation, thesimilarity engine 304 may have indicated that a result included as thefifth document in the set of results documents has a higher level ofsimilarity to the compound SDR of the plurality of preference documentsthan the first four documents. The user preference module 1004 may thenmove the fifth document (or an identification of the fifth document) tothe first position.

The method 1080 includes providing, by the query module, to the thirdcomputing device, the identification of each of the set of resultsdocuments in the modified order (1093). In one embodiment, by performingan analysis of search results as compared to preference documents, thesystem may personalize search results, taking into account the contextof the search in order to select search results likely to be mostimportant to the searcher. As another example, instead of returning anarbitrary number of conventionally ranked results (e.g., first ten orfirst page or other arbitrary number of results), the system couldanalyze thousands of documents and provide only those that aresemantically relevant to the searcher.

In some embodiments, symptoms of a disease may occur in a patient at avery early phase and a medical professional may identify a clear medicaldiagnosis. However, in other embodiments, a patient may present withonly a subset of symptoms and a medical diagnosis is not yet clearlyidentifiable; for example, a patient may provide a blood sample fromwhich the values of ten different types of measurements are determinedand only one of the measurement types has a pathological value while theother nine may be close to a threshold level but remain in a range ofnormal values. It may be challenging to identify a clear medicaldiagnosis in such a case and the patient may be subjected to furthertesting, additional monitoring, and delayed diagnosis while a medicalprofessional waits to see if the remaining symptoms develop. In such anexample, the inability to make an early diagnosis may result in slowertreatment and potentially negative impacts on a health outcome for thepatient. Some embodiments of the methods and systems described hereinaddress such embodiments and provide functionality for supportingmedical diagnoses.

As described above, the system described herein may generate and storeSDRs for numerical data items as well as text-based items and identify alevel of similarity between an SDR generated for a subsequently-receiveddocument and one of the stored SDRs. In some embodiments, if thereceived documents are associated with other data or metadata, such as amedical diagnosis, the system may provide an identification of the dataor metadata (e.g., identifying a medical diagnosis associated with adocument containing numerical data items) as a result of identifying thelevel of similarity.

Referring now to FIG. 11B, in connection with FIG. 11A, a flow diagramdepicts one embodiment of a method 1150 for providing medical diagnosissupport. The method 1150 includes clustering in a two-dimensional metricspace, by a reference map generator executing on a first computingdevice, a set of data documents selected according to at least onecriterion and associated with a medical diagnosis, generating a semanticmap (1152). The method 1150 includes associating, by the semantic map, acoordinate pair with each of the set of data documents (1154). Themethod 1150 includes generating, by a parser executing on the firstcomputing device, an enumeration of measurements occurring in the set ofdata documents (1156). The method 1150 includes determining, by arepresentation generator executing on the first computing device, foreach measurement in the enumeration, occurrence information including:(i) a number of data documents in which the measurement occurs, (ii) anumber of occurrences of the measurement in each data document, and(iii) the coordinate pair associated with each data document in whichthe measurement occurs (1158). The method 1150 includes generating, bythe representation generator, for each measurement in the enumeration asparse distributed representation (SDR) using the occurrence information(1160). The method 1150 includes storing, in an SDR database, each ofthe generated SDRs (1162). The method 1150 includes receiving, by adiagnosis support module executing on a second computing device, from athird computing device, a document comprising a plurality ofmeasurements, the document associated with a medical patient (1164). Themethod 1150 includes generating, by the representation generator, atleast one SDR for the plurality of measurements (1166). The method 1150includes generating, by the representation generator, a compound SDR forthe document, based on the at least one SDR generated for the pluralityof measurements (1168). The method 1150 includes determining, by asimilarity engine executing on the second computing device, a level ofsemantic similarity between the compound SDR generated for the documentand an SDR retrieved from the SDR database (1170). The method 1150includes providing, by the diagnosis support module, to the thirdcomputing device, an identification of the medical diagnosis associatedwith the SDR retrieved from the SDR database, based on the determinedlevel of semantic similarity (1172).

The method 1150 includes clustering in a two-dimensional metric space,by a reference map generator executing on a first computing device, aset of data documents selected according to at least one criterion andassociated with a medical diagnosis, generating a semantic map (1152).In one embodiment, clustering occurs as described above in connectionwith FIG. 2. In some embodiments, each document in the set of documentsincludes a plurality of data items, as above. In one of theseembodiments, however, the plurality of data items is a set of lab valuestaken at one point in time from one sample (e.g., a blood sample from amedical patient); by way of example, the plurality of data items in thedocument may be provided as a comma-separated list of values. As anexample, the system may receive 500 documents, one for each of 500patients, and each document may contain 5 measurements (e.g., 5 valuesof a type of measurement derived from a single blood sample provided byeach patient) and be associated with a medical diagnosis. The system maygenerate the document vectors as described above in connection with FIG.2, using the measurements as data items. In one embodiment, the systemin FIG. 11A includes the functionality described in connection withFIGS. 1A-C and FIG. 3. However, the system in FIG. 11A may have adifferent parser 110 (shown as the lab document parser andpre-processing module 110 b), optimized for parsing documents containinglab values, and the system may include a binning module 150 foroptimizing generation of an enumeration of measurements occurring in theset of data documents as will be discussed in greater detail below.

The method 1150 includes associating, by the semantic map, a coordinatepair with each of the set of data documents (1154). In one embodiment,the generation of a semantic map 108 and the distribution of documentvectors onto the semantic map 108 and the association of coordinatepairs occurs as described above in connection with FIG. 2. By way ofexample, and without limitation, each point in the semantic map 108 mayrepresent one or more documents containing lab values for a type ofmeasurement, such as, without limitation, any type of measurementidentified from a metabolic panel (e.g., calcium per liter). Althoughcertain examples included herein refer to lab values derived from bloodtests, one of ordinary skill in the art will understand that any type ofmedical data associated with a medical diagnosis may be used with themethods and systems described herein.

The method 1150 includes generating, by a parser executing on the firstcomputing device, an enumeration of measurements occurring in the set ofdata documents (1156). In one embodiment, the measurements areenumerated as described above in connection with FIG. 2. In someembodiments, however, the system includes a binning module 150 thatprovides for an optimized process of generating the enumeration. Eachdocument received may contain a plurality of values, each valueidentifying a value of a type of measurement. For example, a documentmay contain a value for a level of calcium in blood—the value is anumber in the document and “calcium” is the type of the measurement.However, the values for each type may vary from one document to another.For example, and without limitation, in a set of 500 documents, thevalues for “calcium” type measurements may range from 0.0 to 5.2mg/liter. In dealing with text-based documents, if a plurality ofdocuments each contains a word then the word is the same in eachdocument—for example, if two documents contain the word “quick,” thetext that forms that word “quick” is the same in each document. Incontrast, when dealing with lab values, two documents could each containa value for the same type of measurement (e.g., a “calcium” typemeasurement or a “glucose” type measurement) but have very differentvalues (e.g., 0.1 and 5.2) each of which is a valid value for the typeof measurement. In order to optimize the system, therefore, the systemmay identify a range of values for each type of measurement included inthe set of documents and provide a user with functionality fordistributing the range substantially evenly into sub-groups; such aprocess may be referred to as binning Performing the binning ensures asignificant amount of overlap among the measurements in a bin. By way ofexample, the system may indicate that there are 5000 values for a“calcium” type measurement in a set of documents, indicate that therange of values is from 0.01-5.2, and provide a user with an option tospecify how to distribute the values. A user may, for example, specifythat values from 0.01-0.3 should be grouped into a first sub-division(also referred to herein as a “bin”), that values from 0.3-3.1 should begrouped into a second sub-division, and that values from 3.1-5.2 shouldbe grouped into a third sub-division. The system may then enumerate howmany of the 5000 values fall into each of the three bins and thatoccurrence information may be used in generating SDRs for each value.The binning module 150 may provide this functionality.

The method 1150 includes determining, by a representation generatorexecuting on the first computing device, for each measurement in theenumeration, occurrence information including: (i) a number of datadocuments in which the measurement occurs, (ii) a number of occurrencesof the measurement in each data document, and (iii) the coordinate pairassociated with each data document in which the measurement occurs(1158). In one embodiment, the occurrence information is information asdescribed above in connection with FIG. 2.

The method 1150 includes generating, by the representation generator,for each measurement in the enumeration, a sparse distributedrepresentation (SDR) using the occurrence information (1160). In oneembodiment, the SDRs are generated as described above in connection withFIG. 2.

The method 1150 includes storing, in an SDR database, each of thegenerated SDRs (1162). In one embodiment, the generated SDRs are storedin the SDR database 120 as described above in connection with FIG. 2.

The method 1150 includes receiving, by a diagnosis support moduleexecuting on a second computing device, from a third computing device, adocument comprising a plurality of measurements, the document associatedwith a medical patient (1164). In one embodiment, the diagnosis supportmodule 1100 receives the document from a client 102 c.

The method 1150 includes generating, by the representation generator, atleast one SDR for the plurality of measurements (1166). In oneembodiment, the diagnosis support module 1100 directs the fingerprintingmodule 302 to generate the SDR as described above in connection withFIGS. 1-3. In one embodiment, the diagnosis support module 1100 directsthe representation generator 114 to generate the SDR as described abovein connection with FIGS. 1-3.

The method 1150 includes generating, by the representation generator, acompound SDR for the document, based on the at least one SDR generatedfor the plurality of measurements (1168). In one embodiment, thediagnosis support module 1100 directs the fingerprinting module 302 togenerate the compound SDR as described above in connection with FIGS.1-3. In one embodiment, the diagnosis support module 1100 directs therepresentation generator 114 to generate the compound SDR as describedabove in connection with FIGS. 1-3.

The method 1150 includes determining, by a similarity engine executingon the second computing device, a level of semantic similarity betweenthe compound SDR generated for the document and an SDR retrieved fromthe SDR database (1170). In one embodiment, the diagnosis support module1100 directs the similarity engine 304 to determine the level ofsemantic similarity as described above in connection with FIGS. 3-5.

The method 1150 includes providing, by the diagnosis support module, tothe third computing device, an identification of the medical diagnosisassociated with the SDR retrieved from the SDR database, based on thedetermined level of semantic similarity (1172). Such a system can detectan approaching medical diagnosis, even when the individual measurementshave not yet reached pathological levels. By feeding a plurality of SDRsand analyzing patterns amongst them, the system can identify changes ina patient's pattern, thus capturing even dynamic processes. For example,a pre-cancer detection system would identify small changes in certainvalues but by having the ability to compare the pattern to the SDRs ofother patients, and analyzing time-based sequences, medical diagnosescan be identified.

In one embodiment, the diagnosis support module 1100 can direct thegeneration of an SDR for even an incomplete parameter vector—for examplein a scenario in which the diagnosis support module 1100 receives aplurality of measurements in a document but the plurality ofmeasurements is missing a measurement of a type relevant to adiagnosis—without degrading results. For instance, as indicated above acomparison between two SDRs can be made and a level of similarityidentified, which may satisfy a threshold level of similarity even ifthe SDRs are not identical; so, even if the SDR generated for a documentwith an incomplete set of measurements is missing a point or two (e.g.,a place on a semantic map 108 at which a more complete document wouldhave had a value for a measurement), a comparison can still be made witha stored SDR. In such an embodiment, the diagnosis support module 1100can identify the at least one parameter that is relevant to a medicaldiagnosis but for which a value was not received and recommend that thevalue be provided (e.g., recommending follow-up procedures or analysesfor missing parameters).

In some embodiments, the documents received may include associations tometadata in addition to a medical diagnosis. For instance, a documentmay also be associated with an identification of patient gender. Suchmetadata may be used to provide confirmation of a level of similaritybetween two SDRs and an identified medical diagnosis. By way of example,the diagnosis support module 1100 may determine that two SDRs aresimilar and identifies a medical diagnosis associated with a documentfrom which one of the SDRs was generated; the diagnosis support module1100 may then apply a rule based on metadata to confirm the accuracy ofthe identification of the medical diagnosis. As an example, and withoutlimitation, a rule may specify that if metadata indicates a patient ismale and the identified medical diagnosis indicates there is a danger ofovarian cancer, instead of providing a user of the client 102 c with theidentified medical diagnosis, the diagnosis support module 1100 shouldinstead report an error (since men do not have ovaries and cannot getovarian cancer).

Referring ahead to FIGS. 13, 14A, and 14B, diagrams depict variousembodiments of methods and systems for generation and use ofcross-lingual sparse distributed representations. In some embodiments,the system 1300 may receive translations of some or all of a set ofdocuments from a first language into a second language and thetranslations may be used to identify corresponding SDRs in a second SDRdatabase generated from the corpus of translated documents. In briefoverview, the system 1300 includes an engine 101, including a secondrepresentation generator 114 b, a second parser and preprocessing module110 c, a translated set of data documents 104 b, a second full-textsearch system 122 b, a second enumeration of data items 112 b, and asecond SDR database 120 b. The engine 101 may be an engine 101 asdescribed above in connection with FIG. 1A.

In brief overview of FIG. 14A, the method 1400 includes clustering, by areference map generator executing on a first computing device, in atwo-dimensional metric space, a set of data documents in a firstlanguage, generating a semantic map, the set of data documents selectedaccording to at least one criterion (1402). The method 1400 includesassociating, by the semantic map, a coordinate pair with each of the setof data documents (1404). The method 1400 includes generating, by afirst parser executing on the first computing device, an enumeration ofterms occurring in the set of data documents (1406). The method 1400includes determining, by a first representation generator executing onthe first computing device, for each term in the enumeration, occurrenceinformation including: (i) a number of data documents in which the termoccurs, (ii) a number of occurrences of the term in each data document,and (iii) the coordinate pair associated with each data document inwhich the term occurs (1408). The method 1400 includes generating, bythe first representation generator, a sparse distributed representation(SDR) for each term in the enumeration, using the occurrence information(1410). The method 1400 includes storing, by the first representationgenerator, in a first SDR database, each of the generated SDRs (1412).The method 1400 includes receiving, by the reference map generator, atranslation, into a second language, of each of the set of datadocuments (1414). The method 1400 includes associating, by the semanticmap, the coordinate pair from each of the set of data documents witheach corresponding document in the translated set of data documents(1416). The method 1400 includes generating, by a second parser, asecond enumeration of terms occurring in the translated set of datadocuments (1418). The method 1400 includes determining, by a secondrepresentation generator, for each term in the second enumeration basedon the translated set of data documents, occurrence informationincluding: (i) a number of translated data documents in which the termoccurs, (ii) a number of occurrences of the term in each translated datadocument, and (iii) the coordinate pair associated with each translateddata document in which the term occurs (1420). The method 1400 includesgenerating, by the second representation generator, for each term in thesecond enumeration, based on the translated set of data documents, anSDR (1422). The method 1400 includes storing, by the secondrepresentation generator, in a second SDR database, each of the SDRsgenerated for each term in the second enumeration. The method 1400includes generating, by the first representation generator, a first SDRof a first document in the first language (1426). The method 1400includes generating, by the second representation generator, a secondSDR of a second document in the second language (1428). The method 1400includes determining a distance between the first SDR and the second SDR(1430). The method 1400 includes providing an identification of a levelof similarity between the first document and the second document (1432).

In one embodiment, (1402)-(1412) are performed as described above inconnection with FIG. 2 (202-214).

The method 1400 includes receiving, by the reference map generator, atranslation, into a second language, of each of the set of datadocuments (1414). In one embodiment, a translation process executed bythe machine 102 a provides the translation to the reference mapgenerator 106. In another embodiment, a human translator provides thetranslation to the engine 101. In still another embodiment, a machinetranslation process provides the translation to the engine 101; themachine translation process may be provided by a third party and mayprovide the translation to the engine 101 directly or across a network.In yet another embodiment, a user of the system 1300 uploads thetranslation to the machine 102 a.

The method 1400 includes associating, by the semantic map, thecoordinate pair from each of the set of data documents with eachcorresponding document in the translated set of data documents (1416).In one embodiment, the semantic map 108 performs the association. Inanother embodiment, the association is performed as described above inconnection with FIG. 2 (204).

The method 1400 includes generating, by a second parser, a secondenumeration of terms occurring in the translated set of data documents(1418). In one embodiment, the generation is performed as describedabove in connection with FIG. 2 (206). In another embodiment, the secondparser is configured (e.g., includes a configuration file) optimizingthe second parser 110 c for parsing documents in the second language.

The method 1400 includes determining, by a second representationgenerator, for each term in the second enumeration based on thetranslated set of data documents, occurrence information including: (i)a number of translated data documents in which the term occurs, (ii) anumber of occurrences of the term in each translated data document, and(iii) the coordinate pair associated with each translated data documentin which the term occurs (1420). In one embodiment, the determination ofoccurrence information is performed as described above in connectionwith FIG. 2 (208).

The method 1400 includes generating, by the second representationgenerator, for each term in the second enumeration, based on thetranslated set of data documents, an SDR (1422). In one embodiment, thegeneration of the term SDRs is performed as described above inconnection with FIG. 2 (210-214).

The method 1400 includes storing, by the second representationgenerator, in a second SDR database, each of the SDRs generated for eachterm in the second enumeration (1424). In one embodiment, the storing ofthe SDRs in the second database is performed as described above inconnection with FIG. 1A.

The method 1400 includes generating, by the first representationgenerator, a first SDR of a first document in the first language (1426).In one embodiment, the generation of the first SDR is performed asdescribed above in connection with FIG. 2.

The method 1400 includes generating, by the second representationgenerator, a second SDR of a second document in the second language(1428). In one embodiment, the generation of the second SDR is performedas described above in connection with FIG. 2.

The method 1400 includes determining a distance between the first SDRand the second SDR (1430). The method 1400 includes providing anidentification of a level of similarity between the first document andthe second document (1432). In one embodiment (1430)-(1432) areperformed as described above in connection with FIGS. 3-4.

In one embodiment, the methods and systems described herein may be usedto provide a measure of quality of a translation system. For example, atranslation system may translate a text from a first language into asecond language and both the text in the first language and thetranslation in the second language may be provided to the systemsdescribed herein; if the system determines that the SDR of the text inthe first language is similar (e.g., exceeds a threshold level ofsimilarity) to the SDR of the translated text (in the second language),then the translation may be said to have a high level of quality.Continuing with this example, if the SDR of the text in the firstlanguage is insufficiently similar (e.g., does not exceed apredetermined threshold level of similarity) to the SDR of thetranslated text (in the second language), then the translation may besaid to have a low level of quality.

Referring now to FIG. 14B, and in connection with FIGS. 13 and 14A, aflow diagram depicts one embodiment of a method 1450. In brief overviewof FIG. 14B, the method 1450 includes clustering, by a reference mapgenerator executing on a first computing device, in a two-dimensionalmetric space, a set of data documents in a first language, generating asemantic map, the set of data documents selected according to at leastone criterion (1452). The method 1450 includes associating, by thesemantic map, a coordinate pair with each of the set of data documents(1454). The method 1450 includes generating, by a first parser executingon the first computing device, an enumeration of terms occurring in theset of data documents (1456). The method 1450 includes determining, by afirst representation generator executing on the first computing device,for each term in the enumeration, occurrence information including: (i)a number of data documents in which the term occurs, (ii) a number ofoccurrences of the term in each data document, and (iii) the coordinatepair associated with each data document in which the term occurs (1458).The method 1450 includes generating, by the first representationgenerator, for each term in the enumeration, a sparse distributedrepresentation (SDR) using the occurrence information (1460). The method1450 includes storing, by the first representation generator, in a firstSDR database, each of the generated SDRs (1462). The method 1450includes receiving, by the reference map generator, a translation, intoa second language, of each of the set of data documents (1464). Themethod 1450 includes associating, by the semantic map, the coordinatepair from each of the set of data documents with each of the translateddata documents (1466). The method 1450 includes generating, by a secondparser, a second enumeration of terms occurring in the translated set ofdata documents (1468). The method 1450 includes determining, by a secondrepresentation generator, for each term in the second enumeration basedon the translated set of data documents, occurrence informationincluding: (i) a number of translated data documents in which the termoccurs, (ii) a number of occurrences of the term in each translated datadocument, and (iii) the coordinate pair associated with each translateddata document in which the term occurs (1470). The method 1450 includesgenerating, by the second representation generator, for each term in thesecond enumeration, based on the translated set of data documents, anSDR (1472). The method 1450 includes storing, by the secondrepresentation generator, in a second SDR database, each of the SDRsgenerated for each term in the second enumeration (1474). The method1450 includes generating, by the first representation generator, a firstSDR of a first term received in the first language (1476). The method1450 includes determining a distance between the first SDR and a secondSDR of a second term in a second language, the second SDR retrieved fromthe second SDR database (1478). The method 1450 includes providing anidentification of the second term in the second language and anidentification of a level of similarity between the first term and thesecond term, based upon the determined distance (1480).

In one embodiment, (1452)-(1474) are performed as described above inconnection with FIG. 14A (1402)-(1424).

The method 1450 includes generating, by the first representationgenerator, a first SDR of a first term received in the first language(1476). In one embodiment, the generation of the first SDR is performedas described above in connection with FIG. 2.

The method 1450 includes determining a distance between the first SDRand a second SDR of a second term in a second language, the second SDRretrieved from the second SDR database (1478). The method 1450 includesproviding an identification of the second term in the second languageand an identification of a level of similarity between the first termand the second term, based upon the determined distance (1480). In oneembodiment (1478)-(1480) are performed as described above in connectionwith FIGS. 3-4.

In another embodiment, the methods and systems described herein may beused to provide an extension to a search system. For example, the system1300 may receive a first term in a first language (e.g., a term a userwishes to use in a query of a search system). The system 1300 maygenerate an SDR of the first term and use the generated first SDR toidentify a second SDR in a second SDR database that satisfies athreshold level of similarity. The system 1300 may then provide thefirst SDR, the second SDR, or both to a search system to enhance theuser's search query, as described above in connection with FIGS. 6A-6C.

In some embodiments, the components described herein may execute one ormore functions automatically, that is, without human intervention. Forexample, the system 100 may receive a set of data documents 104 andautomatically proceed to execute any one or more of the methods forpreprocessing the data documents, training the reference map generator106, or generating SDRs 118 for each data item in the set of datadocuments 104 without human intervention. As another example, the system300 may receive at least one data item and automatically proceed toexecute any one or more of the methods for identifying levels ofsimilarity between the received data item and data items in the SDRdatabase 120, generating enumerations of similar data items, orperforming other functions as described above. As a further example, thesystem 300 may be part of, or include components that are part of, theso-called “Internet of Things” in which autonomous entities execute,communicate, and provide functionality such as that described herein;for instance an automated autonomous process may generate queries,receive responses from the system 300, and provide responses to otherusers (human, computer, or otherwise). In some instances, speech-to-textor text-to-speech based interfaces are included so that, by way ofexample and without limitation, users may generate voice commands thatthe interfaces recognize and with which the interfaces generatecomputer-processable instructions.

In some embodiments, and unlike conventional systems, the systems andmethods described herein bring a semantic context into an individualrepresentation; for example, even without knowing how a particular SDRwas generated, the system can still compare the SDR with another SDR anduse a semantic context of the two SDRs to provide insights to a user. Inother embodiments, and unlike conventional systems, which historicallyfocus on document-level clustering, the systems and methods describedherein use document-level context to provide semantic insights at theterm level, enabling users to identify semantic meaning of individualterms within a corpus of documents.

It should be understood that the systems described above may providemultiple ones of any or each of those components and these componentsmay be provided on either a standalone machine or, in some embodiments,on multiple machines in a distributed system. The phrases ‘in oneembodiment,’ ‘in another embodiment,’ and the like, generally mean thatthe particular feature, structure, step, or characteristic following thephrase is included in at least one embodiment of the present disclosureand may be included in more than one embodiment of the presentdisclosure. Such phrases may, but do not necessarily, refer to the sameembodiment.

Although referred to herein as engines, generators, modules, orcomponents, the elements described herein may each be provided assoftware, hardware, or a combination of the two, and may execute on oneor more machines 100. Although certain components described herein aredepicted as separate entities, for ease of discussion, it should beunderstood that this does not restrict the architecture to a particularimplementation. For instance, the functionality of some or all of thedescribed components may be encompassed by a single circuit or softwarefunction; as another example, the functionality of one or morecomponents may be distributed across multiple components.

A machine 102 providing the functionality described herein may be anytype of workstation, desktop computer, laptop or notebook computer,server, portable computer, mobile telephone, mobile smartphone, or otherportable telecommunication device, media playing device, gaming system,mobile computing device, or any other type and/or form of computing,telecommunications or media device that is capable of communicating onany type and form of network and that has sufficient processor power andmemory capacity to perform the operations described herein. A machine102 may execute, operate or otherwise provide an application, which canbe any type and/or form of software, program, or executableinstructions, including, without limitation, any type and/or form of webbrowser, web-based client, client-server application, an ActiveXcontrol, a JAVA applet, or any other type and/or form of executableinstructions capable of executing on machine 102.

Machines 100 may communicate with each other via a network, which may beany type and/or form of network and may include any of the following: apoint to point network, a broadcast network, a wide area network, alocal area network, a telecommunications network, a data communicationnetwork, a computer network, an ATM (Asynchronous Transfer Mode)network, a SONET (Synchronous Optical Network) network, an SDH(Synchronous Digital Hierarchy) network, a wireless network, and awireline network. In some embodiments, the network may comprise awireless link, such as an infrared channel or satellite band. Thetopology of the network may be a bus, star, or ring network topology.The network may be of any such network topology as known to thoseordinarily skilled in the art capable of supporting the operationsdescribed herein. The network may comprise mobile telephone networksutilizing any protocol or protocols used to communicate among mobiledevices (including tables and handheld devices generally), includingAMPS, TDMA, CDMA, GSM, GPRS, UMTS, or LTE.

The machine 102 may include a network interface to interface to anetwork through a variety of connections including, but not limited to,standard telephone lines, LAN or WAN links (e.g., 802.11, T1, T3, 56 kb,X.25, SNA, DECNET), broadband connections (e.g., ISDN, Frame Relay, ATM,Gigabit Ethernet, Ethernet-over-SONET), wireless connections, or somecombination of any or all of the above. Connections can be establishedusing a variety of communication protocols (e.g., TCP/IP, IPX, SPX,NetBIOS, Ethernet, ARCNET, SONET, SDH, Fiber Distributed Data Interface(FDDI), RS232, IEEE 802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g,IEEE 802.11n, 802.15.4, Bluetooth, ZIGBEE, CDMA, GSM, WiMax, and directasynchronous connections). In one embodiment, the computing device 100communicates with other computing devices 100′ via any type and/or formof gateway or tunneling protocol such as Secure Socket Layer (SSL) orTransport Layer Security (TLS). The network interface may comprise abuilt-in network adapter, network interface card, PCMCIA network card,card bus network adapter, wireless network adapter, USB network adapter,modem, or any other device suitable for interfacing the computing device100 to any type of network capable of communication and performing theoperations described herein.

The systems and methods described above may be implemented as a method,apparatus, or article of manufacture using programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof. The techniques described above may be implementedin one or more computer programs executing on a programmable computerincluding a processor, a storage medium readable by the processor(including, for example, volatile and non-volatile memory and/or storageelements), at least one input device, and at least one output device.Program code may be applied to input entered using the input device toperform the functions described and to generate output. The output maybe provided to one or more output devices.

Each computer program within the scope of the claims below may beimplemented in any programming language, such as assembly language,machine language, a high-level procedural programming language, or anobject-oriented programming language. The programming language may, forexample, be LISP, PROLOG, PERL, C, C++, C#, JAVA, or any compiled orinterpreted programming language.

Each such computer program may be implemented in a computer programproduct tangibly embodied in a machine-readable storage device forexecution by a computer processor. Method steps of the invention may beperformed by a computer processor executing a program tangibly embodiedon a computer-readable medium to perform functions of the invention byoperating on input and generating output. Suitable processors include,by way of example, both general and special purpose microprocessors.Generally, the processor receives instructions and data from a read-onlymemory and/or a random access memory. Storage devices suitable fortangibly embodying computer program instructions include, for example,all forms of computer-readable devices, firmware, programmable logic,hardware (e.g., integrated circuit chip; electronic devices; acomputer-readable non-volatile storage unit; non-volatile memory, suchas semiconductor memory devices, including EPROM, EEPROM, and flashmemory devices; magnetic disks such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROMs). Any of the foregoing may besupplemented by, or incorporated in, specially-designed ASICs(application-specific integrated circuits) or FPGAs (Field-ProgrammableGate Arrays). A computer can generally also receive programs and datafrom a storage medium such as an internal disk (not shown) or aremovable disk. These elements will also be found in a conventionaldesktop or workstation computer as well as other computers suitable forexecuting computer programs implementing the methods described herein,which may be used in conjunction with any digital print engine ormarking engine, display monitor, or other raster output device capableof producing color or gray scale pixels on paper, film, display screen,or other output medium. A computer may also receive programs and datafrom a second computer providing access to the programs via a networktransmission line, wireless transmission media, signals propagatingthrough space, radio waves, infrared signals, etc.

More specifically and in connection to FIG. 12A, an embodiment of anetwork environment is depicted. In brief overview, the networkenvironment comprises one or more clients 1202 a-1202 n in communicationwith one or more remote machines 1206 a-1206 n (also generally referredto as server(s) 1206 or computing device(s) 1206) via one or morenetworks 1204. The machine 102 described above may be provided as amachine 1202, a machine 1206, or any type of machine 1200.

Although FIG. 12A shows a network 1204 between the clients 1202 and theremote machines 1206, the clients 1202 and the remote machines 1206 maybe on the same network 1204. The network 1204 can be a local areanetwork (LAN), such as a company Intranet, a metropolitan area network(MAN), or a wide area network (WAN), such as the Internet or the WorldWide Web. In other embodiments, there are multiple networks 1204 betweenthe clients 1202 and the remote machines 1206. In one of theseembodiments, a network 1204′ (not shown) may be a private network and anetwork 1204 may be a public network. In another of these embodiments, anetwork 1204 may be a private network and a network 1204′ a publicnetwork. In still another embodiment, networks 1204 and 1204′ may bothbe private networks.

The network 1204 may be any type and/or form of network and may includeany of the following: a point to point network, a broadcast network, awide area network, a local area network, a telecommunications network, adata communication network, a computer network, an ATM (AsynchronousTransfer Mode) network, a SONET (Synchronous Optical Network) network,an SDH (Synchronous Digital Hierarchy) network, a wireless network, anda wireline network. In some embodiments, the network 1204 may comprise awireless link, such as an infrared channel or satellite band. Thetopology of the network 1204 may be a bus, star, or ring networktopology. The network 1204 may be of any such network topology as knownto those ordinarily skilled in the art capable of supporting theoperations described herein. The network may comprise mobile telephonenetworks utilizing any protocol or protocols used to communicate amongmobile devices, including AMPS, TDMA, CDMA, GSM, GPRS, or UMTS. In someembodiments, different types of data may be transmitted via differentprotocols. In other embodiments, the same types of data may betransmitted via different protocols.

A client 1202 and a remote machine 1206 (referred to generally ascomputing devices 1200) may be any workstation, desktop computer, laptopor notebook computer, server, portable computer, mobile telephone orother portable telecommunication device, media playing device, a gamingsystem, mobile computing device, or any other type and/or form ofcomputing, telecommunications or media device that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein. In someembodiments, the computing device 1200 may have different processors,operating systems, and input devices consistent with the device. Inother embodiments, the computing device 1200 is a mobile device, digitalaudio player, digital media player, or a combination of such devices. Acomputing device 1200 may execute, operate or otherwise provide anapplication, which can be any type and/or form of software, program, orexecutable instructions, including, without limitation, any type and/orform of web browser, web-based client, client-server application, anActiveX control, or a JAVA applet, or any other type and/or form ofexecutable instructions capable of executing on the computing device1200.

In one embodiment, a computing device 1200 provides functionality of aweb server. In some embodiments, a web server 1200 comprises anopen-source web server, such as the APACHE servers maintained by theApache Software Foundation of Delaware. In other embodiments, the webserver 1200 executes proprietary software, such as the InternetInformation Services products provided by Microsoft Corporation ofRedmond, Wash., the Oracle iPlanet web server products provided byOracle Corporation of Redwood Shores, Calif., or the BEA WEBLOGICproducts provided by BEA Systems of Santa Clara, Calif.

In some embodiments, the system may include multiple, logically groupedcomputing devices 1200. In one of these embodiments, the logical groupof computing devices 1200 may be referred to as a server farm. Inanother of these embodiments, the server farm may be administered as asingle entity.

FIGS. 12B and 12C depict block diagrams of a computing device 1200useful for practicing an embodiment of the client 1202 or a remotemachine 1206. As shown in FIGS. 12B and 12C, each computing device 1200includes a central processing unit 1221, and a main memory unit 1222. Asshown in FIG. 12B, a computing device 1200 may include a storage device1228, an installation device 1216, a network interface 1218, an I/Ocontroller 1223, display devices 1224 a-n, a keyboard 1226, a pointingdevice 1227, such as a mouse, and one or more other I/O devices 1230a-n. The storage device 1228 may include, without limitation, anoperating system and software. As shown in FIG. 12C, each computingdevice 1200 may also include additional optional elements, such as amemory port 1203, a bridge 1270, one or more input/output devices 1230a-1230 n (generally referred to using reference numeral 1230), and acache memory 1240 in communication with the central processing unit1221.

The central processing unit 1221 is any logic circuitry that responds toand processes instructions fetched from the main memory unit 1222. Inmany embodiments, the central processing unit 1221 is provided by amicroprocessor unit, such as: those manufactured by Intel Corporation ofMountain View, Calif.; those manufactured by Motorola Corporation ofSchaumburg, Ill.; those manufactured by Transmeta Corporation of SantaClara, Calif.; those manufactured by International Business Machines ofWhite Plains, N.Y.; or those manufactured by Advanced Micro Devices ofSunnyvale, Calif. Other examples include SPARC processors, ARMprocessors, processors used to build UNIX/LINUX “white” boxes, andprocessors for mobile devices. The computing device 1200 may be based onany of these processors, or any other processor capable of operating asdescribed herein.

Main memory unit 1222 may be one or more memory chips capable of storingdata and allowing any storage location to be directly accessed by themicroprocessor 1221. The main memory 1222 may be based on any availablememory chips capable of operating as described herein. In the embodimentshown in FIG. 12B, the processor 1221 communicates with main memory 1222via a system bus 1250. FIG. 1C depicts an embodiment of a computingdevice 1200 in which the processor communicates directly with mainmemory 1222 via a memory port 1203. FIG. 12C also depicts an embodimentin which the main processor 1221 communicates directly with cache memory1240 via a secondary bus, sometimes referred to as a backside bus. Inother embodiments, the main processor 1221 communicates with cachememory 1240 using the system bus 1250.

In the embodiment shown in FIG. 12B, the processor 1221 communicateswith various I/O devices 1230 via a local system bus 1250. Various busesmay be used to connect the central processing unit 1221 to any of theI/O devices 1230, including a VESA VL bus, an ISA bus, an EISA bus, aMicroChannel Architecture (MCA) bus, a PCI bus, a PCI-X bus, aPCI-Express bus, or a NuBus. For embodiments in which the I/O device isa video display 1224, the processor 1221 may use an Advanced GraphicsPort (AGP) to communicate with the display 1224. FIG. 1C depicts anembodiment of a computer 1200 in which the main processor 1221 alsocommunicates directly with an I/O device 1230 b via, for example,HYPERTRANSPORT, RAPIDIO, or INFINIBAND communications technology.

A wide variety of I/O devices 1230 a-1230 n may be present in thecomputing device 1200. Input devices include keyboards, mice, trackpads,trackballs, microphones, scanners, cameras, and drawing tablets. Outputdevices include video displays, speakers, inkjet printers, laserprinters, and dye-sublimation printers. The I/O devices may becontrolled by an I/O controller 1223 as shown in FIG. 12B. Furthermore,an I/O device may also provide storage and/or an installation device1216 for the computing device 1200. In some embodiments, the computingdevice 1200 may provide USB connections (not shown) to receive handheldUSB storage devices such as the USB Flash Drive line of devicesmanufactured by Twintech Industry, Inc. of Los Alamitos, Calif.

Referring still to FIG. 12B, the computing device 1200 may support anysuitable installation device 1216, such as a floppy disk drive forreceiving floppy disks such as 3.5-inch, 5.25-inch disks or ZIP disks; aCD-ROM drive; a CD-R/RW drive; a DVD-ROM drive; tape drives of variousformats; a USB device; a hard-drive or any other device suitable forinstalling software and programs. In some embodiments, the computingdevice 1200 may provide functionality for installing software over anetwork 1204. The computing device 1200 may further comprise a storagedevice, such as one or more hard disk drives or redundant arrays ofindependent disks, for storing an operating system and other software.

Furthermore, the computing device 1200 may include a network interface1218 to interface to the network 1204 through a variety of connectionsincluding, but not limited to, standard telephone lines, LAN or WANlinks (e.g., 802.11, T1, T3, 56 kb, X.25, SNA, DECNET), broadbandconnections (e.g., ISDN, Frame Relay, ATM, Gigabit Ethernet,Ethernet-over-SONET), wireless connections, or some combination of anyor all of the above. Connections can be established using a variety ofcommunication protocols (e.g., TCP/IP, IPX, SPX, NetBIOS, Ethernet,ARCNET, SONET, SDH, Fiber Distributed Data Interface (FDDI), RS232, IEEE802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, IEEE802.15.4, Bluetooth, ZIGBEE, CDMA, GSM, WiMax, and direct asynchronousconnections). In one embodiment, the computing device 1200 communicateswith other computing devices 1200′ via any type and/or form of gatewayor tunneling protocol such as Secure Socket Layer (SSL) or TransportLayer Security (TLS). The network interface 1218 may comprise a built-innetwork adapter, network interface card, PCMCIA network card, card busnetwork adapter, wireless network adapter, USB network adapter, modem,or any other device suitable for interfacing the computing device 1200to any type of network capable of communication and performing theoperations described herein.

In further embodiments, an I/O device 1230 may be a bridge between thesystem bus 1250 and an external communication bus, such as a USB bus, anApple Desktop Bus, an RS-232 serial connection, a SCSI bus, a FireWirebus, a FireWire 800 bus, an Ethernet bus, an AppleTalk bus, a GigabitEthernet bus, an Asynchronous Transfer Mode bus, a HIPPI bus, a SuperHIPPI bus, a SerialPlus bus, a SCI/LAMP bus, a FibreChannel bus, or aSerial Attached small computer system interface bus.

A computing device 1200 of the sort depicted in FIGS. 12B and 12Ctypically operates under the control of operating systems, which controlscheduling of tasks and access to system resources. The computing device1200 can be running any operating system such as any of the versions ofthe MICROSOFT WINDOWS operating systems, the different releases of theUNIX and LINUX operating systems, any version of the MAC OS forMacintosh computers, any embedded operating system, any real-timeoperating system, any open source operating system, any proprietaryoperating system, any operating systems for mobile computing devices, orany other operating system capable of running on the computing deviceand performing the operations described herein. Typical operatingsystems include, but are not limited to: WINDOWS 3.x, WINDOWS 95,WINDOWS 98, WINDOWS 2000, WINDOWS NT 3.51, WINDOWS NT 4.0, WINDOWS CE,WINDOWS XP, WINDOWS 7, WINDOWS 8, and WINDOWS VISTA, all of which aremanufactured by Microsoft Corporation of Redmond, Wash.; MAC OSmanufactured by Apple Inc. of Cupertino, Calif.; OS/2 manufactured byInternational Business Machines of Armonk, N.Y.; and LINUX, afreely-available operating system distributed by Caldera Corp. of SaltLake City, Utah; Red Hat Enterprise Linux, a Linus-variant operatingsystem distributed by Red Hat, Inc, of Raleigh, N.C.; Ubuntu, afreely-available operating system distributed by Canonical Ltd. ofLondon, England; or any type and/or form of a Unix operating system,among others.

As indicated above, the computing device 1200 can be any type and/orform of computing, telecommunications or media device that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein. The computingdevice 1200 may be a mobile device such as those manufactured, by way ofexample and without limitation, by Apple Inc. of Cupertino, Calif.;Google/Motorola Div. of Ft. Worth, Tex.; Kyocera of Kyoto, Japan;Samsung Electronics Co., Ltd. of Seoul, Korea; Nokia of Finland;Hewlett-Packard Development Company, L.P. and/or Palm, Inc. ofSunnyvale, Calif.; Sony Ericsson Mobile Communications AB of Lund,Sweden; or Research In Motion Limited of Waterloo, Ontario, Canada. Inyet other embodiments, the computing device 1200 is a smart phone,Pocket PC, Pocket PC Phone, or other portable mobile device supportingMicrosoft Windows Mobile Software.

In some embodiments, the computing device 1200 is a digital audioplayer. In one of these embodiments, the computing device 1200 is adigital audio player such as the Apple IPOD, IPOD Touch, IPOD NANO, andIPOD SHUFFLE lines of devices manufactured by Apple Inc. In another ofthese embodiments, the digital audio player may function as both aportable media player and as a mass storage device. In otherembodiments, the computing device 1200 is a digital audio player such asthose manufactured by, for example and without limitation, SamsungElectronics America of Ridgefield Park, N.J., or Creative TechnologiesLtd. of Singapore. In yet other embodiments, the computing device 1200is a portable media player or digital audio player supporting fileformats including, but not limited to, MP3, WAV, M4A/AAC, WMA ProtectedAAC, AEFF, Audible audiobook, Apple Lossless audio file formats, and.mov, .m4v, and .mp4 MPEG-4 (H.264/MPEG-4 AVC) video file formats.

In some embodiments, the computing device 1200 comprises a combinationof devices, such as a mobile phone combined with a digital audio playeror portable media player. In one of these embodiments, the computingdevice 1200 is a device in the Google/Motorola line of combinationdigital audio players and mobile phones. In another of theseembodiments, the computing device 1200 is a device in the iPhonesmartphone line of devices manufactured by Apple Inc. In still anotherof these embodiments, the computing device 1200 is a device executingthe Android open source mobile phone platform distributed by the OpenHandset Alliance; for example, the device 1200 may be a device such asthose provided by Samsung Electronics of Seoul, Korea, or HTCHeadquarters of Taiwan, R.O.C. In other embodiments, the computingdevice 1200 is a tablet device such as, for example and withoutlimitation, the iPad line of devices manufactured by Apple Inc.; thePlayBook manufactured by Research In Motion; the Cruz line of devicesmanufactured by Velocity Micro, Inc. of Richmond, Va.; the Folio andThrive line of devices manufactured by Toshiba America InformationSystems, Inc. of Irvine, Calif.; the Galaxy line of devices manufacturedby Samsung; the HP Slate line of devices manufactured byHewlett-Packard; and the Streak line of devices manufactured by Dell,Inc. of Round Rock, Tex.

Referring now to FIG. 12D, a block diagram depicts one embodiment of asystem in which a plurality of networks provide hosting and deliveryservices. In brief overview, the system includes a cloud services andhosting infrastructure 1280, a service provider data center 1282, and aninformation technology (IT) network 1284.

In one embodiment, the data center 1282 includes computing devices suchas, without limitation, servers (including, for example, applicationservers, file servers, databases, and backup servers), routers,switches, and telecommunications equipment. In another embodiment, thecloud services and hosting infrastructure 1280 provides access to,without limitation, storage systems, databases, application servers,desktop servers, directory services, web servers, as well as servicesfor accessing remotely located hardware and software platforms. In stillother embodiments, the cloud services and hosting infrastructure 1280includes a data center 1282. In other embodiments, however, the cloudservices and hosting infrastructure 1280 relies on services provided bya third-party data center 1282. In some embodiments, the IT network 1204c may provide local services, such as mail services and web services. Inother embodiments, the IT network 1204 c may provide local versions ofremotely located services, such as locally-cached versions ofremotely-located print servers, databases, application servers, desktopservers, directory services, and web servers. In further embodiments,additional servers may reside in the cloud services and hostinginfrastructure 1280, the data center 1282, or other networks altogether,such as those provided by third-party service providers including,without limitation, infrastructure service providers, applicationservice providers, platform service providers, tools service providers,and desktop service providers.

In one embodiment, a user of a client 1202 accesses services provided bya remotely located server 1206 a. For instance, an administrator of anenterprise IT network 1284 may determine that a user of the client 1202a will access an application executing on a virtual machine executing ona remote server 1206 a. As another example, an individual user of aclient 1202 b may use a resource provided to consumers by the remotelylocated server 1206 (such as email, fax, voice or other communicationsservice, data backup services, or other service).

As depicted in FIG. 12D, the data center 1282 and the cloud services andhosting infrastructure 1280 are remotely located from an individual ororganization supported by the data center 1282 and the cloud servicesand hosting infrastructure 1280; for example, the data center 1282 mayreside on a first network 1204 a and the cloud services and hostinginfrastructure 1280 may reside on a second network 1204 b, while the ITnetwork 1284 is a separate, third network 1204 c. In other embodiments,the data center 1282 and the cloud services and hosting infrastructure1280 reside on a first network 1204 a and the IT network 1284 is aseparate, second network 1204 c. In still other embodiments, the cloudservices and hosting infrastructure 1280 resides on a first network 1204a while the data center 1282 and the IT network 1284 form a secondnetwork 1204 c. Although FIG. 1D depicts only one server 1206 a, oneserver 1206 b, one server 1206 c, two clients 1202, and three networks1204, it should be understood that the system may provide multiple onesof any or each of those components. The servers 1206, clients 1202, andnetworks 1204 may be provided as described above in connection withFIGS. 12A-12C.

Therefore, in some embodiments, an IT infrastructure may extend from afirst network—such as a network owned and managed by an individual or anenterprise—into a second network, which may be owned or managed by aseparate entity than the entity owning or managing the first network.Resources provided by the second network may be said to be “in a cloud.”Cloud-resident elements may include, without limitation, storagedevices, servers, databases, computing environments (including virtualmachines, servers, and desktops), and applications. For example, the ITnetwork 1284 may use a remotely located data center 1282 to storeservers (including, for example, application servers, file servers,databases, and backup servers), routers, switches, andtelecommunications equipment. The data center 1282 may be owned andmanaged by the IT network 1284 or a third-party service provider(including for example, a cloud services and hosting infrastructureprovider) may provide access to a separate data center 1282. As anotherexample, the machine 102 a described in connection with FIG. 3 above mayowned or managed by a first entity (e.g., a cloud services and hostinginfrastructure provider 1280) while the machine 102 b described inconnection with FIG. 3 above may be owned or managed by a second entity(e.g., a service provider data center 1282) to which a client 1202connects directly or indirectly (e.g., using resources provided by anyof the entities 1280, 1282, or 1284).

In some embodiments, one or more networks providing computinginfrastructure on behalf of customers is referred to a cloud. In one ofthese embodiments, a system in which users of a first network access atleast a second network, including a pool of abstracted, scalable, andmanaged computing resources capable of hosting resources, may bereferred to as a cloud computing environment. In another of theseembodiments, resources may include, without limitation, virtualizationtechnology, data center resources, applications, and management tools.In some embodiments, Internet-based applications (which may be providedvia a “software-as-a-service” model) may be referred to as cloud-basedresources. In other embodiments, networks that provide users withcomputing resources, such as remote servers, virtual machines, or bladeson blade servers, may be referred to as compute clouds or“infrastructure-as-a-service” providers. In still other embodiments,networks that provide storage resources, such as storage area networks,may be referred to as storage clouds. In further embodiments, a resourcemay be cached in a local network and stored in a cloud.

In some embodiments, some or all of a plurality of remote machines 1206may be leased or rented from third-party companies such as, by way ofexample and without limitation, Amazon Web Services LLC of Seattle,Wash.; Rackspace US, Inc. of San Antonio, Tex.; Microsoft Corporation ofRedmond, Wash.; and Google Inc. of Mountain View, Calif. In otherembodiments, all the hosts 1206 are owned and managed by third-partycompanies including, without limitation, Amazon Web Services LLC,Rackspace US, Inc., Microsoft, and Google.

Having described certain embodiments of methods and systems for mappingdata items to sparse distributed representations, it will now becomeapparent to one of skill in the art that other embodiments incorporatingthe concepts of the disclosure may be used. Therefore, the disclosureshould not be limited to certain embodiments, but rather should belimited only by the spirit and scope of the following claims.

What is claimed is:
 1. A method performed by at least one computerprocessor of each of a plurality of computing devices executing computerprogram instructions stored on at least one non-transitorycomputer-readable medium, wherein the computer program instructions areexecutable by the at least one computer processor to perform a methodfor enhancing a computing networking including a full-text search systemthrough enhancement of queries based upon determining similaritiesbetween data items mapped to sparse distributed representations, themethod comprising: clustering in a two-dimensional metric space, by areference map generator, executing on a first computing device, a set ofdata documents selected according to at least one criterion, generatinga semantic map; associating, by the semantic map, a coordinate pair witheach of the set of data documents; generating, by a parser executing onthe first computing device, an enumeration of data items occurring inthe set of data documents; determining, by a representation generatorexecuting on the first computing device, for each data item in theenumeration, occurrence information including: (i) a number of datadocuments in which the data item occurs, (ii) a number of occurrences ofthe data item in each data document, and (iii) the coordinate pairassociated with each data document in which the data item occurs;generating, by the representation generator, a distributedrepresentation using the occurrence information; receiving, by asparsifying module executing on the first computing device, anidentification of a maximum level of sparsity; reducing, by thesparsifying module, a total number of set bits within the distributedrepresentation based on the maximum level of sparsity to generate asparse distributed representation (SDR) having a normative fillgrade;generating, by the representation generator and the sparsifying module,at least one SDR for each data item in the enumeration of data itemsoccurring in the set of data documents; storing, in an SDR database,each of the generated SDRs; receiving, by a query expansion moduleexecuting on a second computing device, from a third computing device, afirst term; determining, by a similarity engine executing on a fourthcomputing device, a level of semantic similarity between a first SDRgenerated based on the first term and a second SDR of a second term, thesecond SDR retrieved from the SDR database; transmitting, by the queryexpansion module, to a full-text search system, using the first term andthe second term, a query for an identification of each of a subset of asecond set of documents containing at least one term similar to at leastone of the first term and the second term; and transmitting, by thequery expansion module, to the third computing device, theidentification received from the full-text search system of each of thesubset of the second set of documents containing at least one termsimilar to at least one of the first term and the second term.
 2. Themethod of claim 1 further comprising determining a patternrepresentative of semantic contexts in which a data item in the set ofdata documents occurs.
 3. The method of claim 2, wherein a spatialdistribution of coordinate pairs in the pattern reflects at least onesemantic region in a context of which the data item occurred.
 4. Themethod of claim 1, wherein the sparse distributed representationprovides a binary fingerprint of a semantic meaning of the data item. 5.The method of claim 1, wherein associating further comprises associatinga coordinate pair that identifies a location of a point representing oneof the set of data documents in the two-dimensional metric space.
 6. Themethod of claim 1, wherein generating the distributed representationfurther comprises proportionally reducing the total number of set bits,proportional to the number of occurrences of each data item in thedistributed representation.
 7. The method of claim 1, wherein generatingfurther comprises proportionally reducing the total number of set bits,proportional to the number of occurrences of the data in a subset of thedata documents.
 8. The method of claim 1, wherein generating furthercomprises generating a topological map of the sparse distributedrepresentation.
 9. The method of claim 1 further comprising: combining afirst semantic fingerprint of a first data item and a second semanticfingerprint of a second data item to form a compound fingerprint; addinga number of set bits at each location within the compound fingerprint;proportionally reducing a total number of set bits using a thresholdresulting in a normative fillgrade.
 10. The method of claim 9, whereinproportionally reducing further comprises applying a weighting scheme toreduce the total number of set bits, the weighting scheme alsoevaluating a number of bits surrounding a particular set bit.
 11. Asystem for enhancing a computing networking including a full-text searchthrough expansion of queries based upon determining similarities betweendata items mapped to sparse distributed representations, the systemcomprising: a semantic neural network executing on a first computingdevice, clustering, in a two-dimensional metric space, a set of datadocuments selected according to at least one criterion, generating asemantic map, and associating a coordinate pair with each of the set ofdata documents; a parser executing on the first computing device andgenerating an enumeration of data items occurring in the set of datadocuments; a representation generator executing on the first computingdevice, determining, for each data item in the enumeration, occurrenceinformation including: (i) a number of data documents in which the dataitem occurs, (ii) a number of occurrences of the data item in each datadocument, and (iii) the coordinate pair associated with each datadocument in which the data item occurs, and generating, a distributedrepresentation using the occurrence information; a sparsifying moduleexecuting on the first computing device, receiving an identification ofa maximum level of sparsity, and reducing a total number of set bitswithin the distributed representation based on the maximum level ofsparsity to generate a sparse distributed representation (SDR) having anormative fillgrade; wherein the representation generator and thesparsifying module generate at least one SDR for each data item in theenumeration of data items occurring in the set of data documents; aquery expansion module executing on a second computing device andreceiving from a third computing device, a first term; and a similarityengine executing on a fourth computing device, receiving the first termfrom the query expansion module, and determining a level of semanticsimilarity between a first SDR generated based on the first term and asecond SDR of a second term, the second SDR retrieved from the SDRdatabased; wherein the query expansion module transmits to a full-textsearch system, using the first term and the second term, a query for anidentification of each of a subset of a second set of documentscontaining at least one term similar to at least one of the first termand the second term, and wherein the query expansion module transmits,to the third computing device, the identification received from thefull-text search system of each of the subset of the second set ofdocuments containing at least one term similar to at least one of thefirst term and the second term.